JDK-8187567 : [Nestmates] Enable nestmate changes in javac by default
  • Type: Bug
  • Component: tools
  • Sub-Component: javac
  • Affected Version: repo-valhalla
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2017-09-15
  • Updated: 2017-09-21
  • Resolved: 2017-09-21
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.
Other
repo-valhallaFixed
Related Reports
Relates :  
JDK-8187302 - [Nestmates] Prepare for classfile version 54 and javac "release" update
Description
While nestmates will ultimately be associated with a future source/target version of the JDK and an updated classfile version (see JDK-8187302) we want to be able to enable them by default as-if executing in that future release.

The primary changes are confined to javac and are very straight-forward:
- generate the nestmate attributes in the classfile
- use virtual invocation bytecodes for private method invocations
- don't generate private accessors

With this change in place we can update the hotspot nestmate tests to not provide explicit "@compile" directives.
Comments
Changeset: 814d50024bd7 Author: dholmes Date: 2017-09-21 01:21 -0400 URL: http://hg.openjdk.java.net/valhalla/valhalla/langtools/rev/814d50024bd7 Changeset: 45cc25e93c6a Author: dholmes Date: 2017-09-21 03:03 -0400 URL: http://hg.openjdk.java.net/valhalla/valhalla/hotspot/rev/45cc25e93c6a
21-09-2017