[GR-70676] NI-based libjvm shared library.#12689
Merged
Merged
Conversation
to avoid misleading warnings in build output
d517e59 to
2702df5
Compare
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.
This PR add a new NI macro option that allows to build a NI-based
libjvm.soimplementation.Building with
native-image --macro:jvm-libraryprovides the library inThis conveniently allows us to use it with
-XXaltjvm=svm, e.g.The Java launcher passes any system properties or runtime image options down to
libjvm.so.I.e.
java -XXaltjvm=svm -XX:+InterpreterTrace -cp ...does what you would expect and runs Crema with interpreter tracing enabled.Additionally other related fixes are contained in this PR:
libjvm.soto use the system property value forjava.homeat runtime (needed for JRT filesystem access to$JAVA_HOME/lib/modules)ImageNameandImagePath(innative-image.properties) will no more cause misleading warnings in build output