Skip to content
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

release/20.x: [llvm-objcopy][ReleaseNotes] Fix prints wrong path when dump-section output path doesn't exist #125345 #126607

Merged
merged 2 commits into from
Feb 11, 2025

Conversation

AmrDeveloper
Copy link
Member

Add release note for llvm-objcopy fixing prints wrong path when dump-section output path doesn't exist in #125345

@@ -460,6 +460,8 @@ Changes to the LLVM tools
`--localize-symbol`, `--localize-symbols`,
`--skip-symbol`, `--skip-symbols`.

* llvm-objcopy now prints the correct file path in the error message when the output file specified by --dump-section cannot be opened.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

double quotes around the option name.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I made it --dump-section to be similar to all other options in the same file

Copy link
Collaborator

@jh7370 jh7370 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, with @MaskRay's suggestion.

@tstellar tstellar merged commit d43a971 into llvm:release/20.x Feb 11, 2025
16 checks passed
Copy link

@AmrDeveloper (or anyone else). If you would like to add a note about this fix in the release notes (completely optional). Please reply to this comment with a one or two sentence description of the fix. When you are done, please add the release:note label to this PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Development

Successfully merging this pull request may close these issues.

5 participants