-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
LLVM_ERROR when building serde_json in release + debuginfo mode #56265
Labels
A-debuginfo
Area: Debugging information in compiled programs (DWARF, PDB, etc.)
A-LLVM
Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues.
Comments
matthiaskrgr
changed the title
LLVM_ERROR when building release + debuginfo crate
LLVM_ERROR when building serde_json in release + debuginfo mode
Nov 27, 2018
Might be related: racer-rust/racer#1005 |
Closed
It looks like simplifycfg is dropping debugloc on an invoke:
As a first guess, I'd say this is due to rust-lang/llvm@8381d3e. |
I've reported https://bugs.llvm.org/show_bug.cgi?id=39807 upstream. |
nagisa
added
A-LLVM
Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues.
A-debuginfo
Area: Debugging information in compiled programs (DWARF, PDB, etc.)
labels
Nov 27, 2018
A patch has been proposed: https://reviews.llvm.org/D54997 |
Merged
nikic
added a commit
to nikic/rust
that referenced
this issue
Nov 28, 2018
In particular to pull in a fix for rust-lang#56265.
This was referenced Nov 28, 2018
Merged
bors
added a commit
that referenced
this issue
Nov 29, 2018
Update LLVM In particular this fixes #56265. r? @alexcrichton
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
A-debuginfo
Area: Debugging information in compiled programs (DWARF, PDB, etc.)
A-LLVM
Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues.
dummy toml:
RUSTC_WRAPPER="" RUSTFLAGS="" cargo build --release
meta:
Probably caused by #55835
The text was updated successfully, but these errors were encountered: