RFR: JDK-8221766: Load-reference barriers for Shenandoah
Andrew Haley
aph at redhat.com
Fri Apr 5 12:37:38 UTC 2019
On 4/4/19 10:51 AM, Roman Kennke wrote:
> Does all that answer your question? :-)
Sure. One thing that always bothered me about the write barrier was that
it looked fantastically expensive: all of the CPU state was pushed, and
there is a lot of CPU state on AArch64. I never did understand why we can't
have a fast path for that.
--
Andrew Haley
Java Platform Lead Engineer
Red Hat UK Ltd. <https://www.redhat.com>
EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671
More information about the shenandoah-dev
mailing list