-
Notifications
You must be signed in to change notification settings - Fork 13k
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
At debuginfo=0, don't inline debuginfo when inlining #123949
Changes from 4 commits
d05545c
6094063
90b4c86
b8ac5c0
20cf595
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -9,8 +9,6 @@ | |
scope 1 { | ||
} | ||
Comment on lines
9
to
10
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Not related to PR, but this empty scopes looks useless, is they needed? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. These empty ones that aren't from inlining do seem useless to me, but I don't know. As you say, not this PR, so can you open an issue or a zulip thread about this? Cleaning up these scopes after |
||
scope 2 (inlined #[track_caller] <u8 as Add>::add) { | ||
debug self => _2; | ||
debug other => _3; | ||
let mut _4: (u8, bool); | ||
} | ||
|
||
|
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.
Why isn't this
== DebugInfo::Full
? Isn't this current implementation retaining variable debuginfo when compiling withline-tables-only
?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.
Before, it was always copied during inlining, so it at least shouldn't be a regression, right? And when the debuginfo is not set to generate variable debuginfo, shouldn't
var_debug_info
be empty anyway?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.
Yeah, this ought not to be a regression, but I was reading this code and this condition is surprising.
When we load
optimized_mir
for the standard library, it should always have variable debuginfo.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.
Oh, I see. So, I thought about familiarizing myself a bit with the debuginfo handling, I'll try to send a PR that improves this then.