-
Bug
-
Resolution: Fixed
-
P4
-
24
-
b08
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8364290 | 25.0.2 | Chen Liang | P4 | Resolved | Fixed | master |
JDK-8364417 | 25.0.1 | Nibedita Jena | P4 | Resolved | Fixed | b04 |
JDK-8364080 | 25 | Chen Liang | P4 | Resolved | Fixed | b34 |
* If access is aligned then following access modes are supported and are
* guaranteed to support atomic access:
* <ul>
* <li>read write access modes for all {@code T}, with the exception of
* access modes {@code get} and {@code set} for {@code long} and
* {@code double} on 32-bit platforms.
This is misleading, aligned access for modes get/set is supported on 32-bit systems but access is not guaranteed to be atomic and therefore may lead to word tearing.
Note: This is already fixed in MemoryLayout::varHandle.
- backported by
-
JDK-8364080 Clarify VarHandle set/get access on 32-bit platforms
-
- Resolved
-
-
JDK-8364290 Clarify VarHandle set/get access on 32-bit platforms
-
- Resolved
-
-
JDK-8364417 Clarify VarHandle set/get access on 32-bit platforms
-
- Resolved
-
- csr for
-
JDK-8361935 Clarify VarHandle set/get access on 32-bit platforms
-
- Closed
-
- relates to
-
JDK-8315096 Allowed access modes in memory segment should depend on layout alignment
-
- Resolved
-
-
JDK-8318966 Some methods make promises about Java array element alignment that are too strong
-
- Resolved
-
- links to
-
Commit(jdk25) openjdk/jdk/1867effc
-
Commit(master) openjdk/jdk/ea6674fe
-
Review(jdk25) openjdk/jdk/26438
-
Review(master) openjdk/jdk/26258