-
-
Notifications
You must be signed in to change notification settings - Fork 6.8k
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 with old Clang #1179
Comments
How does the exact error message look like? |
[exec] 0 libLLVM-3.4.so 0x00007f42384485d2 llvm::sys::PrintStackTrace(_IO_FILE*) + 34 clang: error: unable to execute command: Segmentation fault (core dumped) |
Yes, I believe that's the one. I wrapped the whole thing inside a |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
I was having the same problem, and I found that if I simply move the swap down under the less specialization, the crash goes away. ¯_(ツ)_/¯ |
@LEgregius Could you provide more details on the fix? @evilsquirrel Could you try the idea from #1179 (comment)? |
It seems to fix the crash, yes. The last time I fixed a compiler crash by swapping lines of code was over 20 years ago, so good catch :)
|
I forked it and made modified version. I'll make a pull request a bit later. |
#1179 Reordered the code. It seems to stop clang 3.4.2 in RHEL 7 from crash…
I am building the library using Clang 3.4.2 (I don't currently have access to a more recent version) and it is crashing the compiler. The crash goes away if I disable the specialization of std::swap at line 17194, and my app still seems to work properly, but I wanted to get a second opinion about how safe this patch actually is...
The text was updated successfully, but these errors were encountered: