-
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
rustc_codegen_ssa: introduce MIR VarDebugInfo, but only for codegen. #65718
Conversation
b2e82f6
to
82e659b
Compare
This comment has been minimized.
This comment has been minimized.
82e659b
to
317e35a
Compare
As per #56231 (comment):
|
This comment has been minimized.
This comment has been minimized.
317e35a
to
2994186
Compare
@@ -149,54 +174,107 @@ impl<'a, 'tcx, Bx: BuilderMethods<'a, 'tcx>> FunctionCx<'a, 'tcx, Bx> { | |||
} | |||
} | |||
|
|||
pub fn debug_declare_locals(&self, bx: &mut Bx) { | |||
let tcx = self.cx.tcx(); | |||
/// Apply debuginfo and/or name, after creating the `alloca` for a local, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎉 for doc-comments
@bors r+ |
📌 Commit 2994186 has been approved by |
📌 Commit 2994186 has been approved by |
rustc_codegen_ssa: introduce MIR VarDebugInfo, but only for codegen. These are all the codegen changes necessary for #56231. The refactors were performed locally to codegen, and in several steps, to ease reviewing and avoid introducing changes in behavior (as I'm not sure our debuginfo tests cover enough). r? @michaelwoerister cc @nagisa @rkruppe @oli-obk
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Weird, why does wasm get no temporaries here? Are we more aggressive somehow? EDIT: more exactly, what's happening here is that on all targets
I can trivially adjust the test so both forms are allowed, but I'm suspicious of the behavior. |
@eddyb this looks simd related and wasm-specific so it's likely related to this configuration option where simd values are passed by-value in wasm and not by-reference, because wasm has entirely different validation/register rules than traditional elf executables. Perhaps it's safe to just ignore the test on wasm? |
In one of my recent PRs I generalized one of the SIMD tests by replacing the |
@alexcrichton Thanks, that definitely explains it! @tlively I'll use |
2994186
to
60a2266
Compare
@bors r=nikomatsakis |
📌 Commit 60a2266 has been approved by |
rustc_codegen_ssa: introduce MIR VarDebugInfo, but only for codegen. These are all the codegen changes necessary for #56231. The refactors were performed locally to codegen, and in several steps, to ease reviewing and avoid introducing changes in behavior (as I'm not sure our debuginfo tests cover enough). r? @michaelwoerister cc @nagisa @rkruppe @oli-obk
☀️ Test successful - checks-azure |
These are all the codegen changes necessary for #56231.
The refactors were performed locally to codegen, and in several steps, to ease reviewing and avoid introducing changes in behavior (as I'm not sure our debuginfo tests cover enough).
r? @michaelwoerister cc @nagisa @rkruppe @oli-obk