[GR-45250] [GR-45734] Strict Dynamic Access Inference

[graalvmbot]

Additions from this PR

The current implementation of the analysis for constant reflection (and other dynamic access) invocations is optimization dependent, leading to the possibility of different image run-time behavior when compiled with different optimization options (specifically related to InlineBeforeAnalysis).

This PR introduced a bytecode-level analysis for such invocations, thus avoiding any graph optimizations.

Two new hosted options are introduced:

• -H:StrictDynamicAccessInference=Disable|Warn|Enforce
  • Disable (default): Disable the strict mode and fall back to the optimization dependent inference for dynamic invocations
  • Warn: Use optimization dependent inference for dynamic invocations, but print a warning for invocations inferred outside of the strict mode
  • Enforce: Infer only dynamic invocations proven to be constant in the strict inference mode
• -H:+ReportDynamicAccessInference
  • Generates a .json report of inferred dynamic access invocations

Review guide

The PR is roughly split into the following components:

• A generic bytecode data-flow analyzer in the com.oracle.svm.hosted.dynamicaccessinference.dataflow package. The main classes here are:
  • com.oracle.svm.hosted.dynamicaccessinference.dataflow.ForwardDataFlowAnalyzer - a generic data flow analyzer;
  • com.oracle.svm.hosted.dynamicaccessinference.dataflow.AbstractInterpreter - an abstract bytecode interpreter built on top of ForwardDataFlowAnalyzer by propagating abstract bytecode execution frames through the data-flow.
• A constant expression analysis utilizing AbstractInterpreter. It is implemented in the com.oracle.svm.hosted.dynamicaccessinference package.

The entry point of the analysis is in the com.oracle.svm.hosted.dynamicaccessinference.StrictDynamicAccessInferenceFeature class. The main steps are:

• Create a com.oracle.svm.hosted.dynamicaccessinference.ConstantExpressionRegistry and register it as an image singleton. The registry maps method and BCI pairs into the abstract frame state before the execution of the corresponding instruction. That abstract state holds the information on constant expressions.
• Analyze every method sent to AnalysisBytecodeParser using a com.oracle.svm.hosted.dynamicaccessinference.ConstantExpressionAnalyzer. The results are stored in the constant expression registry.
• Use the collected analysis results in invocation plugins which target methods such as Class.forName(String).

Additionally, report generation for inferred calls is handled by the com.oracle.svm.hosted.dynamicaccessinference.DynamicAccessInferenceReportFeature feature.

One important implementation detail to note is that ConstantExpressionAnalyzer unwraps analysis methods in order to avoid lookups through the analysis universe, and thus potential unsupported feature exceptions.