[GR-45250][GR-45734] Reachability proofs for reflective operations

[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: Disable the strict mode and fall back to the optimization dependent analysis for inferrable dynamic calls
  • Warn: Fold both the calls inferred with the strict mode analysis and the optimization dependent analysis, but print a warning for non-strict call folding
  • Enforce: Fold only the calls inferred by the strict analysis mode
• -H:DynamicAccessInferenceLog=<location>
  • Outputs a .json log of inferred invocations which would otherwise require a reachability registration to the specified location

Review guide

The PR is roughly split into the following components:

• A generic bytecode data-flow analyzer in the com.oracle.svm.hosted.dataflow package. The main classes here are:
  • com.oracle.svm.hosted.dataflow.ForwardDataFlowAnalyzer - a generic data flow analyzer;
  • com.oracle.svm.hosted.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 state before the execution of the corresponding instruction. That abstract state holds the information on constant expressions.
• Register a com.oracle.svm.hosted.dynamicaccessinference.StrictDynamicAccessInferenceSupport singleton which analyzes every method sent to AnalysisBytecodeParser and ClassInitializerBytecodeParser 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). The full list of targeted methods can be found in the feature class.

Additionally, all logging of inferred calls is handled by the com.oracle.svm.hosted.dynamicaccessinference.DynamicAccessInferenceLoggingFeature 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.

The decision if this functionality is added to --future-defaults can be made after the review and integration tests are complete.