Bug #4016
closedSetting the threshold for generating bytecode
100%
Description
At the level of the EnterpriseConfiguration, it is possible to set the threshold for hotspot bytecode generation by passing an integer (or a string in the form of an integer) to setConfigurationProperty with the Feature key GENERATE_BYTE_CODE.
However, at the Processor level, GENERATE_BYTE_CODE is defined as a boolean, so the only values accepted are true and false.
We should have a separate integer-valued feature to set the hotspot threshold.
Updated by Michael Kay over 5 years ago
- Status changed from New to In Progress
- Applies to branch 9.9 added
- Fix Committed on Branch 9.9 added
Added the property in FeatureKeys.xml and config.xsd. Implemented in EnterpriseConfiguration and ConfigurationReader.
public final static Feature<Integer> THRESHOLD_FOR_HOTSPOT_BYTE_CODE = new Feature<>(
"http://saxon.sf.net/feature/thresholdForHotspotByteCode", 123, EE, Integer.class, null);
Tested in JUnit test.
All that remains is updating the documentation.
Updated by Michael Kay over 5 years ago
- Status changed from In Progress to Resolved
Updated by Debbie Lockett over 5 years ago
Generated java classes Feature, FeatureCode, and FeatureKeys updated on 9.9.
Documentation (including javadoc) will be updated with the next maintenance release.
Updated by Debbie Lockett about 5 years ago
Configuration file schemas in 9.9 samples have now also been updated (to add global/@thresholdForHotspotByteCode).
Updated by O'Neil Delpratt about 5 years ago
- % Done changed from 0 to 100
- Fixed in Maintenance Release 9.9.1.1 added
Bug fix applied to the Saxon 9.9.1.1 maintenance release.
Updated by O'Neil Delpratt about 5 years ago
- Status changed from Resolved to Closed
Please register to edit this issue