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
Compiler crash when using -ftime-trace after 27d8eedd5a3cd7fd644be4f06225ffa1ff04cccf #58551
Comments
@llvm/issue-subscribers-clang-frontend |
Hi, it was my commit that broke the code. I'll make a fix. P. S. I have a silly question =) Your example isn't going to compile? I see there is lack of semicolon after array declaration. Do you test compilation on code with syntaxical errors? |
Yes, I realize it doesn't compile, but this is what the reducer came up with. :) |
A little more detail if you are curious, but the original code that failed was from several micro-benchmarks and real-world code-bases that we build internally. |
Thanks! This compilable sample: struct {
short quantval[4];
} value; also failed with segfault. I made a patch here - https://reviews.llvm.org/D136549, please review it if you have time =) |
The time profiler in `Expr::isIntegerConstantExpr` used to call `Loc->printToString`, it was inconsistent with other time profiles in the file and caused segfaults if `Loc` was `nullptr`. Fixes llvm#58551 Reviewed By: dyung, jloser Differential Revision: https://reviews.llvm.org/D136549
The time profiler in `Expr::isIntegerConstantExpr` used to call `Loc->printToString`, it was inconsistent with other time profiles in the file and caused segfaults if `Loc` was `nullptr`. Fixes llvm#58551 Reviewed By: dyung, jloser Differential Revision: https://reviews.llvm.org/D136549
Internally we have tests that attempt to collect information about the compilation by using
-ftime-trace
and suddenly several of them started to fail with crashes. I bisected the failure back to commit 27d8eed, and reduced the failure to the following:Here is the crash backtrace when compiling the above code with
-c -ftime-trace
:The text was updated successfully, but these errors were encountered: