Repository navigation
Docs: Correct the native-image note on reflection registration - #245
Merged
Merged
Conversation
The result table said the upcall path needs no reflection registration while the build log showed 1,822 types registered and the base metadata registers UpcallTarget. The generated function table needs none; the upcall bootstrap finds its five FFM entry points by name on that one class, which is registered by hand. The log line counts the whole image, JDK and library metadata included. Closes #244
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
1 participant
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.
Closes #244
Documentation corrected:
docs/platforms/graal-native-image-verification.md.UpcallStub.kt), soUpcallTargetis registered by hand inreachability-metadata.base.json.No code change.