Ensure DOTNET_MaxVectorTBitwidth is interpreted as a decimal based input, not hexadecimal #88761
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As per the title, this simply ensures that
DOTNET_MaxVectorTBitWidth=256
is interpreted as256
and not as598
. This will better match user expectations for the value, matches the value users pass into NAOT for the equivalent configuration knob, etc.An equivalent toReinterpretHexAsDecimal
already exists for the JIT config values and is being used by various options, includingPreferredVectorBitWidth
.I missed that
CLRConfig::LookupOptions::ParseIntegerAsBase10
exists and have updated to use that instead.