From: Nick Clifton <nickc@redhat.com>
To: Fangrui Song <i@maskray.me>
Cc: binutils@sourceware.org
Subject: Re: Commit: Add support for displaying unicode characters
Date: Mon, 9 May 2022 17:26:39 +0100 [thread overview]
Message-ID: <8756161e-4ba8-f552-5cf4-d1adcad33534@redhat.com> (raw)
In-Reply-To: <DS7PR12MB5765635B31F15184375B9140CBC79@DS7PR12MB5765.namprd12.prod.outlook.com>
Hi Fangrui,
> I just learned that this patch added -U as an alias for --unicode. In
> macOS nm and llvm-nm, -U is an alias for --defined-only.
> --defined-only seems much more useful than --unicode. I wonder if it
> is too late to redefine -U as --defined-only...
No, it could be changed. I have to say that I would have thought that -d
was a better choice for the short version. But anyway.
Before making the change however, I thought that it would be best to check
to see if there are any other inconsistencies and I did find a couple:
* nm uses -s as the short version of --print-armap, whereas llvm-nm uses -M.
* nm uses -V as the short version of --version, whereas llvm-nm does not have one.
The support/lack of -V does not strike me as important, and it should be a simple
matter to add -M as another short-version of --print-armap, so unless you have
any objections I will create a patch to change -U and add -M.
Cheers
Nick
PS. I also saw that llvm-nm has a -W/--no-weak option which is missing from nm.
Is there a binutils PR filed to add this feature ?
next prev parent reply other threads:[~2022-05-09 16:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-09 13:25 Nick Clifton
2021-11-10 0:42 ` Alan Modra
2021-11-15 13:21 ` Nick Clifton
2022-05-08 5:46 ` Fangrui Song
[not found] ` <DS7PR12MB5765635B31F15184375B9140CBC79@DS7PR12MB5765.namprd12.prod.outlook.com>
2022-05-09 16:26 ` Nick Clifton [this message]
2022-05-10 4:21 ` Fangrui Song
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8756161e-4ba8-f552-5cf4-d1adcad33534@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sourceware.org \
--cc=i@maskray.me \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).