-
Notifications
You must be signed in to change notification settings - Fork 13.5k
[clang] Using -mno-sse2 with 19.1.0 results in frontend command failure #118590
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.
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
Comments
@llvm/issue-subscribers-debuginfo Author: None (shinfd)
While investigating #118152 , I noticed that compiling below code with `clang -mno-sse2` causes compiler to crash.
For some strange reason, modifying the whitespaces seem to change the outcome (details at the end). Please refer to the Compiler Explorer sample for the exact code: https://godbolt.org/z/3Y3xoefnG The error log:
Reproduces with trunk and 19.1.0. Not observed with 18 or earlier. Starting from the Compiler Explorer sample, removing blank line between include and function made the code compile successfully. Trunk clang also compiles OK when all indentation tabs are replaced with whitespaces, but 19.1.0 still showed error. |
Yet another duplicate of #29774. |
Apology for missing that; thought I went through the past issues |
No worries, #29774 is quite old by now, and because it was never properly fixed, people keep running into it... :( |
While investigating #118152 , I noticed that compiling below code with
clang -mno-sse2
causes compiler to crash.For some strange reason, modifying the whitespaces seem to change the outcome (details at the end). Please refer to the Compiler Explorer sample for the exact code: https://godbolt.org/z/3Y3xoefnG
The error log:
Reproduces with trunk and 19.1.0. Not observed with 18 or earlier.
Starting from the Compiler Explorer sample, removing blank line between include and function made the code compile successfully. Trunk clang also compiles OK when all indentation tabs are replaced with whitespaces, but 19.1.0 still showed error.
The text was updated successfully, but these errors were encountered: