Repository navigation
Test driver transfers from positioned numeric buffer slices - #53
Draft
RicheyWorks wants to merge 1 commit into
Draft
RicheyWorks wants to merge 1 commit into
RicheyWorks wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add real driver-transfer coverage for
Pointer.toBufferwith a nonzero slice origin and a nonzero position, covering heap and direct buffers for byte, short, int, long, float and double. The existing position-aware copy tests concentrate on float buffers and the runtime host-to-host path.Each of the 12 parameterized cases copies exactly three elements host→device→heap and verifies values 4,5,6 plus unchanged source position/limit. The largest device allocation is 24 bytes. A private executor thread owns each temporary context; both allocation and context are cleaned up in
finally. No kernels, device resets, or global exception-mode changes.This matrix exposed the shared-JNI copy-back bug addressed separately by jcuda/jcuda-common#4. It is a companion regression, not a second production fix.
CharBufferis omitted because its support is still pending in #51; the other draft Java fixes and #52 are not included in this independent branch.Validation:
-Xcheck:jnibecause of the shared release-mode bug.-Xcheck:jni, with the exact loaded DLL confirmed by JVM logging.Example focused invocation after rebuilding the native driver with the common fix: