-
Notifications
You must be signed in to change notification settings - Fork 13.1k
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
Two codegen fixes #113775
Two codegen fixes #113775
Conversation
PR rust-lang#112946 tweaked the naming of LLVM threads, but messed things up slightly, resulting in threads on Windows having names like `optimize module {} regex.f10ba03eb5ec7975-cgu.0`. This commit removes the extraneous `{} `.
@@ -36,10 +34,6 @@ pub struct PerLocalVarDebugInfo<'tcx, D> { | |||
/// `DIVariable` returned by `create_dbg_var`. | |||
pub dbg_var: Option<D>, | |||
|
|||
/// Byte range in the `dbg_var` covered by this fragment, | |||
/// if this is a fragment of a composite `VarDebugInfo`. | |||
pub fragment: Option<Range<Size>>, |
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.
I think this field actually needs to be used to produce correct debuginfo for composite debuginfo variables.
// DWARF is concerned, it's not really a fragment. | ||
None | ||
} else { | ||
Some(fragment_start..fragment_start + fragment_layout.size) |
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.
This codepath is taken if the MIR SROA pass is enabled.
I have moved the "Fix LLVM thread names on Windows" commit to #113879. |
A couple of small things.
r? @wesleywiser