[GR-69713] Adopt JVMCI separation from AnnotatedElement. #12547
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR migrates all usages of
AnnotatedElementAPIs, such asgetAnnotation,getAnnotations,getDeclaredAnnotations, and parameter annotation retrieval, from the JVMCI type hierarchy and user code. The APIs inAnnotationValueSupportandAnnotationUtilcentered aroundAnnotationValueand now provide equivalent functionality, better aligned to both HotSpot and non-HotSpot environments. This resolves the major design limitation where reflection-based annotation APIs only worked reliably when JVMCI was running on HotSpot.In compiler code, annotation queries use
AnnotationValueSupportand are thus limited to annotations represented asAnnotationValueobjects. Annotation elements are accessed by name (e.g.annotation.getInt("count")).In SVM code, annotation queries make use of
AnnotationUtilto obtainAnnotationobjects and thus have access to typed element accessors (e.g.annotation.count()).Required LabsJDK PR: graalvm/labs-openjdk#17