Hi, thanks for your replies.
If I leave out the -Xbootclasspath stuff, then it blows up because of some clash (I think it uses its old javac.jar in the normal classpath then). I can't check it right now, but iirc, it found the signer information of some javac related class is different than the signer information of another class in the same package or such. I'm currently using it for testing. I can skip the compiler benchmarks for now. However, it is a nice test-benchmark because it does lots and lots of allocations, would be nice to have it working. I hope SPEC releases an updated SPECjvm soon. It has been somewhat broken since JDK8, and now even more... Regards, Roman Am Donnerstag, den 08.01.2015 um 11:10 +0000 schrieb Alan Bateman: > On 07/01/2015 22:15, Jonathan Gibbons wrote: > > : > > > > Alan, > > > > In this context, javac.jar does not so much contain "a utility for > > transforming .java files .class files" as much as "a significant body > > of open source code suitable for testing the performance of a JVM". > > In that context, it would not be appropriate to change javac.jar more > > than necessary. > > > Right, if Roman is running SPECjvm98 for benchmark purposes (as opposed > to using it as part of a quality test run) then upgrading javac means it > would be a different benchmark. However some change (maybe > -bootclasspath as you suggest) is required because it seems to be an > older version of javac that doesn't know anything about the new runtime > image. > > -Alan
