-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
debuginfo: Handle spread_arg case in MIR-trans in a more stable way. #37153
Conversation
…or the individual pieces.
@bors r+ |
📌 Commit 8d5b523 has been approved by |
Yay - this fix also appears to work when applied to 1.12.0! The backport just needs to change the |
The change should certainly be unproblematic. |
⌛ Testing commit 8d5b523 with merge dcb6fbe... |
💔 Test failed - auto-win-gnu-32-opt-rustbuild |
Failure was transient (git crashed during clone), retry? |
@bors retry |
debuginfo: Handle spread_arg case in MIR-trans in a more stable way. Use `VariableAccess::DirectVariable` instead of `VariableAccess::IndirectVariable` in order not to make LLVM's SROA angry. This is a step towards fixing #36774 and #35547. At least, I can build Cargo with optimizations + debuginfo again. r? @eddyb
💔 Test failed - auto-mac-64-opt-rustbuild |
@bors: retry On Sun, Oct 16, 2016 at 7:21 AM, bors notifications@github.com wrote:
|
💔 Test failed - auto-win-gnu-32-opt |
@bors: retry On Sun, Oct 16, 2016 at 4:49 PM, bors notifications@github.com wrote:
|
debuginfo: Handle spread_arg case in MIR-trans in a more stable way. Use `VariableAccess::DirectVariable` instead of `VariableAccess::IndirectVariable` in order not to make LLVM's SROA angry. This is a step towards fixing #36774 and #35547. At least, I can build Cargo with optimizations + debuginfo again. r? @eddyb
Accepting for beta. Small patch, regression. cc @rust-lang/compiler |
Use
VariableAccess::DirectVariable
instead ofVariableAccess::IndirectVariable
in order not to make LLVM's SROA angry. This is a step towards fixing #36774 and #35547. At least, I can build Cargo with optimizations + debuginfo again.r? @eddyb