On Wed, 23 Aug 2023 18:26:03 GMT, Chris Plummer wrote:
>> During [JDK-8151815](https://bugs.openjdk.org/browse/JDK-8151815) it was
>> noted that the PerfMemory _initialized and _destroyed fields should be
>> volatile, but VMStructs didn't have the needed support for doing that, so it
>> was le
On Wed, 23 Aug 2023 18:26:03 GMT, Chris Plummer wrote:
>> During [JDK-8151815](https://bugs.openjdk.org/browse/JDK-8151815) it was
>> noted that the PerfMemory _initialized and _destroyed fields should be
>> volatile, but VMStructs didn't have the needed support for doing that, so it
>> was le
On Wed, 23 Aug 2023 18:26:03 GMT, Chris Plummer wrote:
>> During [JDK-8151815](https://bugs.openjdk.org/browse/JDK-8151815) it was
>> noted that the PerfMemory _initialized and _destroyed fields should be
>> volatile, but VMStructs didn't have the needed support for doing that, so it
>> was le
On Wed, 23 Aug 2023 18:26:03 GMT, Chris Plummer wrote:
>> During [JDK-8151815](https://bugs.openjdk.org/browse/JDK-8151815) it was
>> noted that the PerfMemory _initialized and _destroyed fields should be
>> volatile, but VMStructs didn't have the needed support for doing that, so it
>> was le
> During [JDK-8151815](https://bugs.openjdk.org/browse/JDK-8151815) it was
> noted that the PerfMemory _initialized and _destroyed fields should be
> volatile, but VMStructs didn't have the needed support for doing that, so it
> was left as a future task. @YaSuenag provided a patch at the time t
