[8] Heads-up: Borked EA after LRB backports?

[Roman Kennke]

I only tried to do what 11 and up do there (it's done via GC interface in newer versions) Maybe I got it wrong though.?

Roman


Am 25. Oktober 2019 17:51:11 MESZ schrieb Roland Westrelin <rwestrel at redhat.com>:
>
>> Please push it to sh/jdk8 under e.g. "Fix
>ShenandoahLoadReferenceBarrierNode::{Value, Identity}
>> signatures after LRB backport".
>
>Done. But this doesn't seem right either:
>
>diff -r e040b7d17b6f src/share/vm/opto/escape.cpp
>--- a/src/share/vm/opto/escape.cpp	Fri Oct 25 17:22:36 2019 +0200
>+++ b/src/share/vm/opto/escape.cpp	Fri Oct 25 17:49:32 2019 +0200
>@@ -2991,7 +2991,6 @@
>                n->is_CheckCastPP() ||
>                n->is_EncodeP() ||
>                n->is_DecodeN() ||
>-               n->Opcode() == Op_ShenandoahLoadReferenceBarrier ||
>                (n->is_ConstraintCast() && n->Opcode() == Op_CastPP)) {
>       if (visited.test_set(n->_idx)) {
>         assert(n->is_Phi(), "loops only through Phi's");

-- 
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.