From: Jan Beulich <jbeulich@suse.com>
To: Ilya Kuklin <ikuklin@accesssoftek.com>
Cc: "binutils@sourceware.org" <binutils@sourceware.org>
Subject: Re: objcopy: A potentially new option --ignore-symbol(s)
Date: Fri, 23 Feb 2024 09:16:42 +0100 [thread overview]
Message-ID: <698666f6-4b89-4f4e-bfea-996c194182e3@suse.com> (raw)
In-Reply-To: <SA1PR20MB4370E48A764B18FCEC28F6E1C6572@SA1PR20MB4370.namprd20.prod.outlook.com>
On 22.02.2024 18:51, Ilya Kuklin wrote:
> There is an option in the making for llvm-objcopy called --ignore-symbol(s).
> We would like to have some feedback about the name of the option
> and its functionality.
>
> The functionality of this option is to ignore the specified symbols when
> executing other options that can change the symbol's name, binding or
> visibility, so that their parameters remain unchanged.
I think e.g. "skip" would be more appropriate than "ignore".
> For example, when executing an option --localize-hidden, specifying an
> existing hidden symbol with --ignore-symbol will keep its binding from
> being changed.
Question is how useful a single negative option is when perhaps you want
to do multiple adjustments at the same time, with different sets needing
exclusion. Imo separate negative options (e.g. --no-localize-hidden)
would be more suitable in the long run.
Jan
> Purpose:
> This option is needed mostly to support cases where there is a need to
> change parameters of a vast number of symbols with exception of a few
> specific symbols. Writing a negative pattern is much simpler than many
> positive patterns that avoid a certain case. Plus, since there is an option
> --keep-symbol that does exactly this but for removing symbols, there
> should also be one that keeps symbols' parameters from being changed.
>
> If an option with the same functionality is going to be introduced at some
> point to binutils objcopy, please consider naming it the same way or
> suggest an alternative.
>
> Feel free to join the discussion:
> https://github.com/llvm/llvm-project/pull/80873
>
> --
> Thanks,
> Ilya Kuklin
next prev parent reply other threads:[~2024-02-23 8:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-22 17:51 Ilya Kuklin
2024-02-23 8:16 ` Jan Beulich [this message]
2024-02-27 18:56 Ilya Kuklin
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=698666f6-4b89-4f4e-bfea-996c194182e3@suse.com \
--to=jbeulich@suse.com \
--cc=binutils@sourceware.org \
--cc=ikuklin@accesssoftek.com \
/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).