Mark Reinhold suggested during the review of JDK-8137173:
"We don't want to create another sun.misc-like dumping ground
with jdk.internal. We should prefer small, descriptive subpackages
for things like this so that, when they are (inevitably) exposed via
-XaddExports, their exposure can be limited.
I suggest putting this into jdk.internal.vm.annotation, which is also a
good place for the ReservedStackAccess annotation envisioned in JEP 270
(http://openjdk.java.net/jeps/270)."
----
Additional suggestion from Mark: Please rename the annotation to
@IntrinsicCandidate There's no need for the "HotSpot" prefix any more
since this annotation will now be in a package that is reserved for
VM-specific annotations.
(Sorry for this late suggestion; this just came up in a parallel
discussion of the JEP 270's @ReservedStackAccess annotation.)
"We don't want to create another sun.misc-like dumping ground
with jdk.internal. We should prefer small, descriptive subpackages
for things like this so that, when they are (inevitably) exposed via
-XaddExports, their exposure can be limited.
I suggest putting this into jdk.internal.vm.annotation, which is also a
good place for the ReservedStackAccess annotation envisioned in JEP 270
(http://openjdk.java.net/jeps/270)."
----
Additional suggestion from Mark: Please rename the annotation to
@IntrinsicCandidate There's no need for the "HotSpot" prefix any more
since this annotation will now be in a package that is reserved for
VM-specific annotations.
(Sorry for this late suggestion; this just came up in a parallel
discussion of the JEP 270's @ReservedStackAccess annotation.)
- relates to
-
JDK-8140687 Move @Contended to the jdk.internal.vm.annotation package
-
- Resolved
-
-
JDK-8137173 @HotSpotIntrinsicCandidate is not Oracle-specific
-
- Resolved
-
-
JDK-8129882 Improve consistency of HotSpot-specific annotations
-
- Open
-