llvm segfaults during bootstrap of rustc_middle in stage 1 #76213
Comments
|
cc @eddyb |
jonas-schievink
added
A-LLVM
|
@matthiaskrgr: Was a coredump generated? If so, should be able to generate a backtrace by running |
does this help? |
|
config.toml via [llvm]
thin-lto = true
ninja = true
targets = "X86"
link-jobs = 2
[build]
extended = true
tools = ["cargo", "rls", "clippy", "rustfmt", "analysis", "src", "miri", "rust-analyzer"]
sanitizers = true
profiler = true
low-priority = true
[install]
[rust]
codegen-units = 0
backtrace-on-ice = true
[target.x86_64-unknown-linux-gnu]
ar = "llvm-ar"
ranlib = "llvm-ranlib"
[dist] |
|
There is no segfault if I build without |
|
Marking this as P-high based on the wg-prioritization discussion |
Dylan-DPC-zz
added
P-high
|
@matthiaskrgr: What setup are you using to pass |
|
I had
|
|
@petrochenkov was hitting segfaults with LLD with target-cpu=native, but that was on MSVC: #76398 |
|
Hmm, I think i also have my linker set to lld, but I'm on linux... |
|
Still crashes after llvm update in #77063 |
|
I got the same SIGSEGV with config.toml: Can't reproduce it with bootstrap from 1.47 to 1.47 |
|
some users hit it in gentoo with 1.48.0 removing |
|
I ran into the same problem: rustc exited with signal: 9 Caused by:������������������������������� process didn't exit successfully: expected success, got: exit code: 101 |
When bootstrapping rustc, I can observe a crash inside llvm when building
stage 1rustc_middle.In
dmsgI could see this:I did a bisect and found out that the crash happens since 1d22f75
cc @davidtwco
my cpu is a
Intel(R) Core(TM) i5-7200U CPUThe timing of the crash makes me think that this might happen somewhere during LTOing of the rustc_middle crate, rustc did not show a backtrace for the crash though, since it happens inside llvm.
I already did purge my rustc build cache and the sccache before I saw the segfault happens inside llvm (it didn't help anyway). 😅
rustc @ d9cd4a3
The text was updated successfully, but these errors were encountered: