Bug ID: JDK-6460352 Reintroduce Scope.dble

JDK-6460352 : Reintroduce Scope.dble

Type: Bug
Component: tools
Sub-Component: javac
Affected Version: 6,7

Priority: P3
Status: Closed
Resolution: Duplicate
OS: generic
CPU: generic

Submitted: 2006-08-15
Updated: 2013-04-26
Resolved: 2013-04-26

Versions (Unresolved/Resolved/Fixed)

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 6	JDK 7	Other
6-poolResolved	7Fixed	OpenJDK6Resolved

Related Reports

Duplicate :	JDK-6998063 - new Scope impl to fix Scope performance issues
Duplicate :	JDK-6887978 - compilation very slow for classes with many fields
Relates :	JDK-6449122 - javac process is failing on Mustang integration compile
Relates :	JDK-6998063 - new Scope impl to fix Scope performance issues
Relates :	JDK-6996626 - Scope fix issues for ImportScope

Description

A short term fix for 6449122 was to remove the use of Scope.dble.
A different fix should be researched in order to reintroduce Scope.dble.

Comments

EVALUATION http://hg.openjdk.java.net/jdk7/build/langtools/rev/601160d857ef

04-12-2010

EVALUATION Further investigation (see 6449122) reveals that Scope.dble is not safe. We may need to completely rewrite scopes early in JDK 7 development in order to encapsulate the scope implementation and provide a common abstraction for scopes.

30-09-2006

EVALUATION Before Scope.dble can be reintroduced, a reliable test case must be developed.

15-08-2006