Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Ensure DOTNET_MaxVectorTBitwidth is interpreted as a decimal based input, not hexadecimal #88761

Merged
merged 2 commits into from
Jul 13, 2023
Merged

Ensure DOTNET_MaxVectorTBitwidth is interpreted as a decimal based input, not hexadecimal #88761

merged 2 commits into from
Jul 13, 2023

Commits on Jul 12, 2023

  1. Ensure DOTNET_MaxVectorTBitwidth is interpreted as a decimal based in… 

    …put, not hexadecimal
    @tannergooding
    tannergooding committed Jul 12, 2023
    Configuration menu
    Copy the full SHA
    5a40dcf View commit details
    Browse the repository at this point in the history

  2. Use CLRConfig::LookupOptions::ParseIntegerAsBase10 instead

    @tannergooding
    tannergooding committed Jul 12, 2023
    Configuration menu
    Copy the full SHA
    0d20237 View commit details
    Browse the repository at this point in the history