8299090: Specify coordinate order for additional CaptureCallState parameters on class as well
Reviewed-by: pminborg, mcimadamore
This commit is contained in:
parent
945ef07564
commit
3918f9f523
@ -303,8 +303,8 @@ public sealed interface Linker permits AbstractLinker {
|
||||
* before it can be overwritten by the Java runtime, or read through conventional means}
|
||||
* <p>
|
||||
* A downcall method handle linked with this option will feature an additional {@link MemorySegment}
|
||||
* parameter directly following the target address parameter. This memory segment must be a
|
||||
* native segment into which the captured state is written.
|
||||
* parameter directly following the target address, and optional {@link SegmentAllocator} parameters.
|
||||
* This memory segment must be a native segment into which the captured state is written.
|
||||
*
|
||||
* @param capturedState the names of the values to save.
|
||||
* @see CaptureCallState#supported()
|
||||
@ -323,6 +323,10 @@ public sealed interface Linker permits AbstractLinker {
|
||||
* <p>
|
||||
* Execution state is captured by a downcall method handle on invocation, by writing it
|
||||
* to a native segment provided by the user to the downcall method handle.
|
||||
* For this purpose, a downcall method handle linked with the {@link #captureCallState(String[])}
|
||||
* option will feature an additional {@link MemorySegment} parameter directly
|
||||
* following the target address, and optional {@link SegmentAllocator} parameters.
|
||||
* This parameter represents the native segment into which the captured state is written.
|
||||
* <p>
|
||||
* The native segment should have the layout {@linkplain CaptureCallState#layout associated}
|
||||
* with the particular {@code CaptureCallState} instance used to link the downcall handle.
|
||||
|
Loading…
x
Reference in New Issue
Block a user