-
Bug
-
Resolution: Fixed
-
P2
-
19, 20, 21, 22, 23
-
b09
-
Verified
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8326321 | 22.0.1 | Paul Sandoz | P2 | Resolved | Fixed | b05 |
JDK-8325256 | 22 | Paul Sandoz | P2 | Resolved | Fixed | b35 |
JDK-8329865 | 21.0.4-oracle | Ravi Reddy | P2 | Closed | Fixed | b04 |
JDK-8325856 | 21.0.3 | Aleksey Shipilev | P2 | Resolved | Fixed | b04 |
This is an oversight and explicit bounds checks are required, as is already case for the other load and store memory access methods (including storing to memory memory segments).
The workaround is to call the static method {T}Vector::fromMemorySegment.
The fix is for the implementation(s) of VectorSpecies::fromMemorySegment to do the same and call {T}Vector::fromMemorySegment, following the same pattern for implementations of VectorSpecies::fromArray.
- backported by
-
JDK-8325256 [vectorapi] Bounds checking issues when accessing memory segments
- Resolved
-
JDK-8325856 [vectorapi] Bounds checking issues when accessing memory segments
- Resolved
-
JDK-8326321 [vectorapi] Bounds checking issues when accessing memory segments
- Resolved
-
JDK-8329865 [vectorapi] Bounds checking issues when accessing memory segments
- Closed
- links to
-
Commit openjdk/jdk21u-dev/786c5fb1
-
Commit openjdk/jdk22/9cc260d3
-
Commit openjdk/jdk/1ae85138
-
Review openjdk/jdk21u-dev/237
-
Review openjdk/jdk22/109
-
Review openjdk/jdk/17621