<html><head></head><body>Looks good, thanks.<br>Roman<br><br><div class="gmail_quote">Am 6. Juni 2019 18:41:43 MESZ schrieb Aleksey Shipilev <shade@redhat.com>:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="k9mail">RFE:<br> <a href="https://bugs.openjdk.java.net/browse/JDK-8225357">https://bugs.openjdk.java.net/browse/JDK-8225357</a><br><br>Currently the method can return NULL on the path where something else is contending over the write.<br>In most current cases, that path works correctly, but not when something else (for example, inline<br>fixup in barrier taken by Java thread) updates the references on their own.<br><br>Then, the CAS might fail (as it should), and the GC code would think that thread is responsible to<br>show the object to the marking code. This is risky and would lead to bugs. Instead, we would want to<br>reply with the most actual reference at all times.<br><br>Webrev:<br> <a href="http://cr.openjdk.java.net/~shade/8225357/webrev.01/">http://cr.openjdk.java.net/~shade/8225357/webrev.01/</a><br><br>Testing: hotspot_gc_shenandoah<br></pre></blockquote></div><br>-- <br>Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.</body></html>