RFR (S) 8175887: C1 value numbering handling of Unsafe.get*Volatile is incorrect (original) (raw)
Vladimir Ivanov vladimir.x.ivanov at oracle.com
Thu Mar 2 20:57:29 UTC 2017
- Previous message: RFR (S) 8175887: C1 value numbering handling of Unsafe.get*Volatile is incorrect
- Next message: Fwd: RFR: 8175917: [JVMCI] Avoid long JNI handle chains
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Feel free to send approval request. Nightlies look clean.
Best regards, Vladimir Ivanov
On 3/2/17 11:08 PM, Aleksey Shipilev wrote:
Hi again,
If you see no troubles in nightly runs, can you propose this to 8u? I can propose myself, if you want. -Aleksey On 03/01/2017 02:41 PM, Vladimir Ivanov wrote: Pushed: http://hg.openjdk.java.net/jdk9/hs/hotspot/rev/2ff05d967fb2
Best regards, Vladimir Ivanov On 3/1/17 12:01 AM, Aleksey Shipilev wrote: On 02/28/2017 10:01 PM, Vladimir Ivanov wrote:
http://cr.openjdk.java.net/~vlivanov/shade/8175887/ The cleanup look good, but are you sure AssertionError would get reported from the thread, and it would not silently die? The original test exited hard to handle this. Good point. Reverted that part. (Updated the webrev in place.) Thumbs up. Thanks for handling this! -Aleksey
- Previous message: RFR (S) 8175887: C1 value numbering handling of Unsafe.get*Volatile is incorrect
- Next message: Fwd: RFR: 8175917: [JVMCI] Avoid long JNI handle chains
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the hotspot-compiler-dev mailing list