I built a copy of hotspot from b33 on ubuntu with gcc 4.2 and I'm
seeing the same failure you are. I believe this is the same issue
covered by 6741642 which was found and fixed by the IcedTea folks.
Applying the fix to a copy of b33 allowed dacapo to complete
normally. 6741642 is in the hotspot-comp repository but won't trickle
up into a promoted build for a couple weeks so you may need to apply
this by hand to your version. http://hg.openjdk.java.net/jdk7/hotspot-comp/hotspot/rev/fa4d1d240383
is the changeset of interest.
tom
On Aug 28, 2008, at 1:34 AM, Luca Martini wrote:
Tom Rodriguez wrote:
Could you be more specific about what bits you are running, i.e.
which
changeset of hotspot? The official openjdk bits run fine for me
with at
least b30-b33.
It seems b33.
[EMAIL PROTECTED]:~/mp/interfaces/OpenJDK/jdk7/hotspot$ hg log | head -n 6
changeset: 241:5b3b8a69f10f
tag: tip
user: xdono
date: Thu Aug 14 09:26:23 2008 -0700
summary: Added tag jdk7-b33 for changeset 585535ec8a14
Bloat is not the only dacapo benchmark to fail, but also
antlr, chart, eclipse, fop, jython, lusearch, pmd, xalan.
hsqldb and luindex do not fail.
I think it is definitively a problem of my OpenJDK build.
Once the build finished, to use the new VM, is it necessary to set
some
environemnt variable or invoking the new java executable will suffice?
I also put on pastebin my make sanity:
http://pastebin.com/f52ad5606
Do you see something strange?
Thanks for all your help.
Luca
--
*****************************************
Ing. Luca Martini
Dipartimento di Ing. dell'Informazione
Università di Pisa
Via Diotisalvi, 2, I-56126 Pisa, Italy
Tel: +39 050 2217 465
Fax: +39 050 2217 600
e-mail: [EMAIL PROTECTED]
*****************************************
