JDK-6350086 : Increase compiler optimisation level for libfontmanager to improve runtime performance
- Type: Bug
- Component: client-libs
- Sub-Component: 2d
- Affected Version: 1.4.0
- Priority: P3
- Status: Resolved
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2005-11-14
- Updated: 2010-04-02
- Resolved: 2005-12-05
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.
| Other | JDK 6 |
|---|---|
| 1.4.2_11Fixed | 6 b63Fixed  |
Description
libfontmanager in JDK is built with default compiler optimisation flags. By increasing it to a higher level as used on most other libraries, some tests which attemp to exercise some of that native code can run 5-20% faster on Windows and Solaris. This particularly will help cases where complex text layout is used as that uses a significant amount of native C++ code in libfontmanager. There is a small increase in disk footprint - amounting to just about 30Kbytes on Windows 32 bit but this is presumably also in line with what is already happening in all other libs.
Comments
|