-
Notifications
You must be signed in to change notification settings - Fork 13.6k
Closed
Labels
A-LLVMArea: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues.Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues.C-bugCategory: This is a bug.Category: This is a bug.I-crashIssue: The compiler crashes (SIGSEGV, SIGABRT, etc). Use I-ICE instead when the compiler panics.Issue: The compiler crashes (SIGSEGV, SIGABRT, etc). Use I-ICE instead when the compiler panics.P-highHigh priorityHigh priorityT-compilerRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.regression-from-stable-to-nightlyPerformance or correctness regression from stable to nightly.Performance or correctness regression from stable to nightly.
Description
The unwinding
crate compiles on nightlies before e2b52ff (the LLVM 15 upgrade), but now it fails with this:
$ cargo +nightly build --target x86_64-unknown-linux-gnu
Compiling libc v0.2.132
Compiling gimli v0.26.2
Compiling unwinding v0.1.4 (/private/tmp/unwinding)
inlinable function call in a function with debug info must have a !dbg location
call void @_Unwind_Resume(ptr %81) #15
inlinable function call in a function with debug info must have a !dbg location
call void @_Unwind_Resume(ptr %101) #15
inlinable function call in a function with debug info must have a !dbg location
call void @_Unwind_Resume(ptr %144) #15
inlinable function call in a function with debug info must have a !dbg location
call void @_Unwind_Resume(ptr %111) #15
LLVM ERROR: Broken module found, compilation aborted!
error: could not compile `unwinding`
The error happens both when natively compiling on Arch Linux, and when cross compiling from macOS as shown here.
Meta
rustc --version --verbose
:
rustc 1.65.0-nightly (c07a8b4e0 2022-08-26)
binary: rustc
commit-hash: c07a8b4e09f356c7468b69c50cac7fc5b5000b8a
commit-date: 2022-08-26
host: x86_64-apple-darwin
release: 1.65.0-nightly
LLVM version: 15.0.0
Bisect output
searched nightlies: from nightly-2022-08-12 to nightly-2022-08-14 [originally searched from 2022-07-01; reduced range shown here because I restarted bisect due to a crash half way through]
regressed nightly: nightly-2022-08-13
searched commit range: 20ffea6...f22819b
regressed commit: e2b52ff
bisected with cargo-bisect-rustc v0.6.4
Host triple: x86_64-unknown-linux-gnu
Reproduce with:
cargo bisect-rustc --end=2022-08-14
Metadata
Metadata
Assignees
Labels
A-LLVMArea: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues.Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues.C-bugCategory: This is a bug.Category: This is a bug.I-crashIssue: The compiler crashes (SIGSEGV, SIGABRT, etc). Use I-ICE instead when the compiler panics.Issue: The compiler crashes (SIGSEGV, SIGABRT, etc). Use I-ICE instead when the compiler panics.P-highHigh priorityHigh priorityT-compilerRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.regression-from-stable-to-nightlyPerformance or correctness regression from stable to nightly.Performance or correctness regression from stable to nightly.
Type
Projects
Milestone
Relationships
Development
Select code repository
Activity
apiraino commentedon Aug 31, 2022
WG-prioritization assigning priority (Zulip discussion).
@rustbot label -I-prioritize +P-high T-compiler
nikic commentedon Aug 31, 2022
Upstream issue: llvm/llvm-project#57469
Not sure why this starts with LLVM 15, as the issue itself is not new.
Update LLVM submodule