RFR: JDK-8199735: Mark word updates need to use Access API (original) (raw)
Roman Kennke rkennke at redhat.com
Mon Mar 19 11:07:08 UTC 2018
- Previous message (by thread): RFR: JDK-8199735: Mark word updates need to use Access API
- Next message (by thread): RFR: JDK-8199735: Mark word updates need to use Access API
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Am 19.03.2018 um 11:40 schrieb Roman Kennke:
Currently, the mark word is accessed directly in oopDesc::mark() setmark() and a bunch of other accessors. Those need to use the Access API instead because GC might want to employ barriers on those accesses, pretty much like every other field in oopDesc.
Notice that this is not about accessing the bits and fields inside the markOop, but about accessing the header itself. http://cr.openjdk.java.net/~rkennke/JDK-8199735/webrev.01/ Testing: build fastdebug/release with and without PCH, passed tier1 fastdebug/release. Can I please get reviews? Thanks, Roman
Just when I sent it, I realized that this is dropping the volatile from the mark word access. Fixed here:
http://cr.openjdk.java.net/~rkennke/JDK-8199735/webrev.02/
-------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: OpenPGP digital signature URL: <https://mail.openjdk.org/pipermail/hotspot-gc-dev/attachments/20180319/3d496fd7/signature.asc>
- Previous message (by thread): RFR: JDK-8199735: Mark word updates need to use Access API
- Next message (by thread): RFR: JDK-8199735: Mark word updates need to use Access API
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]