-
Notifications
You must be signed in to change notification settings - Fork 729
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
Improvements for Relocatable Compilations #2921
Comments
Request: Documentation to help developers understand when they need to add a new validation record. |
@mstoodle @vijaysun-omr @mpirvu @jdmpapin I've updated this issue to reflect the fact that there is only one OMR and OpenJ9 PR each (so that guys know which is the canonical PR for review purposes) |
It doesn't seem like it, but is any update to the user guide required for this change? New command line options or diagnostics or ? |
No new updates; there are a couple of JIT options to control the new infrastructure, but I don't know if that should be explicitly documented (considering that the goal is to have the new infrastructure eventually be the default). |
Some duplication with what's here, but an issue to collect the OMR pieces of ongoing work is here: eclipse-omr/omr#3029 . |
@dsouzai - any update? |
Code was delivered yesterday to OpenJ9. So this is now done for v0.11 of OpenJ9. |
The improvements for the 0.12 release have been delivered. This will continue in the next release. |
Ongoing issue tracking improvements for AOT
TR::SymbolValidationManager::storeValidationRecordIfNecessary
Clean up the logic inTR::SymbolValidationManager::storeValidationRecordIfNecessary
#3032isClassVisible
to remember the answer Add a validation record for isClassVisible #4765canDevirtualizeDispatch
does not impact trivial devirtualization opportunities under AOT Revisit canDevirtualizeDispatch query under AOT #3030Related OMR issue:
eclipse-omr/omr#3029
The text was updated successfully, but these errors were encountered: