[9] RFR(XS): 8137173: @HotSpotIntrinsicCandidate is not Oracle-specific (original) (raw)
mark.reinhold at oracle.com mark.reinhold at oracle.com
Thu Oct 15 21:12:49 UTC 2015
- Previous message: [9] RFR(XS): 8137173: @HotSpotIntrinsicCandidate is not Oracle-specific
- Next message: [9] RFR(XS): 8137173: @HotSpotIntrinsicCandidate is not Oracle-specific
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
2015/10/1 10:57 -0700, zoltan.majo at oracle.com:
On 10/01/2015 05:54 PM, mark.reinhold at oracle.com wrote:
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). I filed an RFE, JDK-8138732: "move @HotSpotIntrinsicCandidate to the jdk.internal.vm.annotation package" [1], to track the issue of moving the annotation to a different package. I hope I can take care of it soon. Thank you and best regards,
Thanks. While you're at it, could you 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 discussion of the @ReservedStackAccess annotation for JEP 270, which is also destined for the jdk.internal.vm.annotation package.)
(I've pasted this addendum into JDK-8138732.)
- Mark
- Previous message: [9] RFR(XS): 8137173: @HotSpotIntrinsicCandidate is not Oracle-specific
- Next message: [9] RFR(XS): 8137173: @HotSpotIntrinsicCandidate is not Oracle-specific
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]