-
Notifications
You must be signed in to change notification settings - Fork 171
Generate debug information for assembly functions #213
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
Conversation
Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @korken89 (or someone else) soon. If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes. Please see the contribution instructions for more information. |
To be clear: this makes our object files larger, but shouldn't have any impact on application code size, right? |
It makes the final ELF files bigger, the debug information for the assembly function will always be there, regardless of the rustc settings. The actual code size without debug information is unchanged. For an embedded context, this is probably more relevant. |
Sorry, yes, I mean "the final occupied space in the target flash" is unchanged, whereas we don't really care if the elfs are a few bytes larger. |
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.
bors r+
Build failed: |
We'll have to wait for #214 which I thought would merge before this. |
bors retry |
Build failed: |
bors retry |
Build succeeded: |
This helps with debugging, but makes the binaries a bit larger.