Open dsouzai opened 5 years ago
@mstoodle @vijaysun-omr @mpirvu @jdmpapin
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 ? https://www.eclipse.org/openj9/docs/aot/
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: https://github.com/eclipse/omr/issues/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
https://github.com/eclipse/openj9/issues/3032isClassVisible
to remember the answer https://github.com/eclipse/openj9/issues/4765canDevirtualizeDispatch
does not impact trivial devirtualization opportunities under AOT https://github.com/eclipse/openj9/issues/3030Related OMR issue: https://github.com/eclipse/omr/issues/3029