Escape characters in section names in map files #1551
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Rangi42
added
enhancement
Rangi42
force-pushed
the
map-names
branch
2 times, most recently
from
3b44756
to
df74ff4
Compare
This makes size-0 sections print as "($0000 bytes)" instead of "(0 bytes)", which is more consistent.
ISSOtm
approved these changes
Oct 23, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
With the second commit here, this slightly changes .map file output: a zero-byte section is printed as "
($0000 bytes)", instead of "(0 bytes)". This is more consistent with other "($xxxx bytes)" sections, and with the sizes ofEMPTYspace.