FTR, there's a good smoke test for the method handles part of JSR 292 in the
JDK sources:
davinci/sources/jdk/test/java/dyn/MethodHandlesTest.java
Running the test requires JUnit 4.5.
$JSR292_JAVA_HOME/bin/java -ea -esa
-XX:+{UnlockExperimentalVMOptions,EnableMethodHandles}
-Xbootclasspath/a:$HOME/env/jars/junit-4.5.jar org.junit.runner.JUnitCore
test.java.dyn.MethodHandlesTest
The source file shows a number of known failures currently excluded from the
test suite. (But the exclusions are decreasing over time!)
The latest patch push (including meth-ing-6939134.patch) upgrades this test,
and passes it cleanly.
-- John
On Apr 4, 2010, at 7:56 PM, Stephen Bannasch wrote:
> At 10:41 PM +0200 4/2/10, Attila Szegedi wrote:
>> So I decided to throw in the towel, and use Stephen Bannasch's excellent
>> "update.sh"
>> from<http://gist.github.com/raw/243072/c2e862bec37bde76f904cbed53b4e95f6ddd6c52/update.sh>
>>
>> It now bombs with:
>>
>> /Users/aszegedi/Documents/projects/openjdk/bsd-port/hotspot/src/share/vm/opto/runtime.cpp:
>> In static member function 'static u_char* OptoRuntime::rethrow_C(oopDesc*,
>> JavaThread*, u_char*)':
>> /Users/aszegedi/Documents/projects/openjdk/bsd-port/hotspot/src/share/vm/opto/runtime.cpp:955:
>> error: no matching function for call to
>> 'SharedRuntime::raw_exception_handler_for_return_address(JavaThread*&,
>> u_char*&)'
>> /Users/aszegedi/Documents/projects/openjdk/bsd-port/hotspot/src/share/vm/runtime/sharedRuntime.hpp:101:
>> note: candidates are: static u_char*
>> SharedRuntime::raw_exception_handler_for_return_address(u_char*)
>> make[6]: *** [runtime.o] Error 1
>> make[6]: *** Waiting for unfinished jobs....
>> make[5]: *** [the_vm] Error 2
>> make[4]: *** [product] Error 2
>> make[3]: *** [generic_build2] Error 2
>> make[2]: *** [product] Error 2
>> make[1]: *** [hotspot-build] Error 2
>> make: *** [build_product_image] Error 2
>>
>> Digging backwards I can see this:
>>
>> + (cd sources/hotspot; hg qpush -a)
>> abort: local changes found, refresh first
>> *** Exit status 255.
>>
>> Does this mean that the current MLVM hotspot patches can't be applied to the
>> tip of the bsd-port/hotspot?
>> (Or am I doing something wrong?)
>
> Hi Attila,
>
> I've had that problem in the past. I think if I took the time to understand
> hg better the issue would be pretty clear. I solvedthe problem by recreating
> my local source repo (and added the instructions for doing this as comments
> in update.sh). Since then I have not had any errors where I couldn't update
> because of local changes.
>
> There have been times when the bsd-port code hasn't built properly for a
> while on 10.5 but that isn't the case now.
>
> I just built the latest bsd-port w/mlvm patches and it seems to work.
>
> I've uploaded a copy here:
> http://www.concord.org/~sbannasch/mlvm/java-1.7.0-internal-2010_04_04.tar.gz
>
> _______________________________________________
> mlvm-dev mailing list
> mlvm-dev@openjdk.java.net
> http://mail.openjdk.java.net/mailman/listinfo/mlvm-dev
_______________________________________________
mlvm-dev mailing list
mlvm-dev@openjdk.java.net
http://mail.openjdk.java.net/mailman/listinfo/mlvm-dev
