JDK-8144826 : [JVMCI] Remove jdk.vm.ci.hotspot.Stable and use jdk.internal.vm.annotation.Stable
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 9
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2015-12-07
  • Updated: 2016-06-09
  • Resolved: 2016-05-11
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 9
9 b122Fixed
Related Reports
Blocks :  
Blocks :  
Description
JDK-8144223 moves the package private java.lang.invoke.Stable (among others) to a public annoation of the non-exported package jdk.internal.vm.annotation.

JVMCI's  jdk.vm.ci.hotspot.Stable can be removed and dependencies updated to use jdk.internal.vm.annotation.Stable.
Comments
No objections if you wanna treat it as an enhancement, feel free to update.
13-04-2016

Shouldn't we treat this issue as enhancement?
11-04-2016

Currently JVMCI is compiled by the boot JDK. Until this changes, perhaps with the Jigsaw integration?, this issue is blocked. In addition a qualified export will be required in java.base: exports jdk.internal.vm.annotation to jdk.vm.ci; It is also assumed that classes in the jdk.vm.ci module are privileged code, see src/share/vm/classfile/classFileParser.cpp: const bool privileged = loader_data->is_the_null_class_loader_data() || loader_data->is_ext_class_loader_data() || loader_data->is_anonymous(); If this is not the case some form of additional checking will be required for classes of trusted modules.
07-12-2015