-
Notifications
You must be signed in to change notification settings - Fork 721
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Delay AOT validation until restore under -XX:+DebugOnRestore #19316
Conversation
@mpirvu could you please review? |
@mpirvu review reminder. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
jenkins test sanity all jdk17 |
Build failure:
|
Ah, I didn't guard the static field initialization with |
Under -XX:+DebugOnRestore, the JIT generates FSD code. This is problematic for AOT as either: 1. An existing SCC will fail validation, since the AOT code therein will not have been generated with FSD, or 2. An unpopulated SCC will contain FSD code, which will be useless for any JVM that does not have FSD enabled This commit delays AOT validation until after restore; this ensures that AOT code from the SCC can be loaded post-restore, and that any code added to the SCC is maximally sharable. Signed-off-by: Irwin D'Souza <[email protected]>
5facf9e
to
b1bcfa7
Compare
jenkins test sanity all jdk17 |
win64 failure because all nodes were offline |
Merging since tests have passed (windows failures are due to infra) |
Under -XX:+DebugOnRestore, the JIT generates FSD code. This is problematic for AOT as either:
This commit delays AOT validation until after restore; this ensures that AOT code from the SCC can be loaded post-restore, and that any code added to the SCC is maximally sharable.
Parent issue: #18866