RFR(XS): 8031188: Fix for 8029015: PPC64 (part 216): opto: trap based null and range checks (original) (raw)
Lindenmaier, Goetz goetz.lindenmaier at sap.com
Mon Jan 6 02:14:50 PST 2014
- Previous message: JDK-6584008 (jvmtiStringPrimitiveCallback should not be invoked when string value is null) in 1.7.0_45
- Next message: RFR(XS): 8031188: Fix for 8029015: PPC64 (part 216): opto: trap based null and range checks
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
A happy new year everybody!
Could you please review and test this tiny fix? It's in code so far only used by ppc64. http://cr.openjdk.java.net/~goetz/webrevs/8031188-nc/
fixup_flow can add new blocks with a branch instruction. Doing so after a trap based check added the branch behind the wrong Proj node. The branch would jump to the proper target, but build_oop_map analyses a wrong control flow.
Fix: Swap the Projs in the block list so that the new block is added behind the proper node.
Thanks & best regards, Goetz
- Previous message: JDK-6584008 (jvmtiStringPrimitiveCallback should not be invoked when string value is null) in 1.7.0_45
- Next message: RFR(XS): 8031188: Fix for 8029015: PPC64 (part 216): opto: trap based null and range checks
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]