-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Rustc 1.32 segfaults with llvm 7.0.1 while building fd-find and lto=true enabled #57801
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
also cc @sharkdp |
fd also seems to use lto: https://github.com/sharkdp/fd/blob/master/Cargo.toml#L60 |
I was also able to reproduce this bug, when compiling my own project cntr with lto optimization enabled. |
Duplicate of #57762 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
While binaries by provided by mozilla are compiled against its bundled llvm, distributions such as archlinux, fedora and NixOS link rust against the upstream llvm version.
Also the rust project itself don't has this version yet, it might be still useful to track this issue here as it will eventually also affect the project if they ever upgrade llvm.
Steps to reproduce:
This happens both on archlinux (#61490) and on NixOS (#54323). Both distributions uses llvm 7.0.1 instead of the llvm version that is provided by rust. The problem goes away when using the vendored llvm source.
This is backtrace of the coredump: https://gist.github.com/e337646429c41d93a089aaa45b8d2375
as generated by
gdb rustc core -batch -ex bt
.The error suggest that it might be related to generating debugging symbols.
cc @foutrelis
UPDATE: the error also seems to go away, when I disable lto optimization.
The text was updated successfully, but these errors were encountered: