RFR: JDK-8199612: Replace remaining uses of G1BarrierSet::enqueue() with appropriate Access API calls (original) (raw)
Roman Kennke rkennke at redhat.com
Wed Mar 14 20:34:12 UTC 2018
- Previous message (by thread): RFR: JDK-8199612: Replace remaining uses of G1BarrierSet::enqueue() with appropriate Access API calls
- Next message (by thread): RFR: JDK-8199620: Support for JNI object pinning
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Am 14.03.2018 um 15:30 schrieb Roman Kennke:
We still have 2 places where we call directly to G1BarrierSet::enqueue(), those should use the appropriate Access API instead.
Bug: https://bugs.openjdk.java.net/browse/JDK-8199612 Webrev: http://cr.openjdk.java.net/~rkennke/8199612/webrev.00/ Passes: tier1runtime tests, currently running all of tier1 Please review! Thanks, Roman
Apparently this is already being worked on elsewhere. I'm withdrawing this RFR and bug-report.
Thanks, Roman
-------------- 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/20180314/e320e9e5/signature.asc>
- Previous message (by thread): RFR: JDK-8199612: Replace remaining uses of G1BarrierSet::enqueue() with appropriate Access API calls
- Next message (by thread): RFR: JDK-8199620: Support for JNI object pinning
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]