-
Notifications
You must be signed in to change notification settings - Fork 67
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
No dwarf #51
No dwarf #51
Conversation
…tting This skips checking all of our items for whether they have names or not (which they won't if we aren't configured to emit names, but we don't need to do that big traversal in this case).
src/module/mod.rs
Outdated
@@ -256,9 +256,17 @@ impl Module { | |||
self.funcs.emit(&mut cx); | |||
self.data.emit(&mut cx); | |||
|
|||
emit_name_section(&mut cx); | |||
if self.config.generate_names { |
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 so the generate_names
here was intended for debugging passes in walrus itself, so a lot of debug information is tied to this currently. I think we may want a separate flag (on by default whereas the generate_names
flag is off by default) to emit the name section?
self.producers.emit(&mut cx); | ||
for section in self.custom.iter() { | ||
if !self.config.generate_dwarf && section.name.starts_with(".debug") { |
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 wonder if this should also be skipped when parsing to avoid keeping the dwarf sections in memory?
…ems` Since this is not about generating the name section or not, but whether we give names like "f0" to anonymous functions
No description provided.