-
Notifications
You must be signed in to change notification settings - Fork 15.3k
[llvm-objcopy] Let --change-section-lma change segments wth filesz=0,… #127724
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
Merged
Merged
Changes from 1 commit
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
5e39ac8
[llvm-objcopy] Let --change-section-lma change segments wth filesz=0,…
jonathonpenix 3d23251
fixup! [llvm-objcopy] Let --change-section-lma change segments wth fi…
jonathonpenix 91ebc90
fixup! [llvm-objcopy] Let --change-section-lma change segments wth fi…
jonathonpenix File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
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.
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.
Should this check simply be
if (Seg.MemSize > 0)? The difference would be that sections with file size and zero mem size would not be changed, but such segments are only valid if they are not PT_LOAD segments and presumably aren't part of the loaded file image.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 didn't have a particularly principled reason for not doing this in the first place. Broadly, I was seeing such segments (non-PT_LOAD, filesize >0, memsize = 0) generated by ld.bfd for ex: the RISC-V
PT_RISCV_ATTRIBUTESsegment, and GNU objcopy seemed to modify the LMA but also would at times touch the offset/filesize/memsize in ways I didn't entirely follow. As such, I tried to err towards being consistent with our previous behavior here (to modify such segments).That said, I think what you said about "presumably aren't part of the loaded file image" seems correct to me, so I went ahead and made the change/added an explicit test for this/updated the description--hopefully this looks reasonable!