JDK-6957080 : MethodComparator needs stress testing
- Type: Bug
- Component: hotspot
- Sub-Component: compiler
- Affected Version: 7
- Priority: P3
- Status: Resolved
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2010-05-29
- Updated: 2010-09-24
- Resolved: 2010-06-26
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.
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 |
|---|---|---|
| 6u21pFixed | 7Fixed  |
hs19Fixed |
Description
The MethodComparator module is only run when classes are replaced. It should be stress-tested on more methods. In particular, changes to the constant pool index accessors have caused one bug in MethodComparator 6957004. This bug proposes to (a) add a stress testing flag for MethodComparator which will compare every method to itself immediately after loading, (b) run this stress test on at least 25,000 methods, and (c) fix whatever bugs make methods fail to compare equal to themselves.
Comments
|