JDK-6474281 : why do we have a class named 'sparc' when it seems to be a special keyword?
  • Type: Bug
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 6,7
  • Priority: P4
  • Status: Closed
  • Resolution: Fixed
  • OS: generic,solaris
  • CPU: generic,sparc
  • Submitted: 2006-09-22
  • Updated: 2012-10-08
  • Resolved: 2006-11-14
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
6u4Fixed 7Fixed hs10Fixed
Related Reports
Duplicate :  
If you compile to a .i file in the jvmg build directory and try to use CC on the .i file the 'sparc' keyword reappears and you get compilation errors, which makes it hard to diagnose problems in the CC compilers.

I don't see any reason for the naming of this class sparc instead of 'Sparc' which is actually our naming convention (first letter uppercase in class names).

EVALUATION Fixed 6474281 Rename class sparc to class Sparc 'sparc' appears to be a predefined macro with the sparcWorks tools which makes debugging compiler problems by creating a preprocessor output file not work.

EVALUATION Changed name to "Sparc" which is our naming convention for classes (leading uppercase character) which is not a predefined macro.