JDK-6472143 : extend CompilerOracle with per compile flags
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 7
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: solaris_9
  • CPU: sparc
  • Submitted: 2006-09-18
  • Updated: 2010-04-02
  • 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
Often when making changes in the compiler it can be useful to have flags that are set for particular compiles as a way to narrow down the cause of performance differences.  It's also useful for experimentation since you can special behaviour.  This similar to the print command in the CompilerOracle but generalized to arbitrary strings.  It can be used to wrap around existing compilation flags or to make up new flags as needed during development.

SUGGESTED FIX http://analemma.sfbay.sun.com/net/prt-archiver.sfbay/data/archived_workspaces/main/c2_baseline/2006/20060919162924.never.options/workspace/webrevs/webrev-2006.09.19/index.html

EVALUATION Added a new syntax in the oracle like so: option java/lang/String hashCode foo Then in the VM if you have a methodOop or ciMethod that refers to String.hashCode you can say method->has_option("foo") and it will return true