-
Notifications
You must be signed in to change notification settings - Fork 738
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
Allow relocation of ClassUnload assumptions #2672
Conversation
This is the openj9 part of eclipse-omr/omr#2880 |
@dmitry-ten I recommend you try and get this merged sooner rather than later; pretty soon I'm going to have to deliver my AOT changes and it's going to conflict with this pretty hard. |
How do I rerun the tests? |
@mpirvu could you review? |
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.
At first I didn't understand how a classUnloadAssumption with -1 for the class pointer can work at all, but Irwin pointed me to code that scans the RAT and patches all locations for which such assumptions exist.
Jenkins test all all jdk8 |
8555d9d
to
a7812be
Compare
AOT and JITaaS require assumptions to be relocated. Add a new kind of ExternalRelocation to relocate ClassUnload assumptions. Signed-off-by: Dmitry Ten <Dmitry.Ten@ibm.com>
a7812be
to
0d8f5d6
Compare
Fixed missing commas in |
@mpirvu I think this can be merged now. |
Jenkins test all all jdk8 |
Extended tests fail for an unrelated reason (some attach test). |
Yes, failures seem unrelated to this change. |
AOT and JITaaS require assumptions to be relocated.
Add a new kind of ExternalRelocation to relocate
ClassUnload assumptions.
Signed-off-by: Dmitry Ten Dmitry.Ten@ibm.com