From: Alexandre Oliva <oliva@adacore.com>
To: Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>,
Nathan Sidwell <nathan@acm.org>,
Eric Botcazou <ebotcazou@adacore.com>,
Jan Hubicka <hubicka@ucw.cz>,
"Joseph S. Myers" <joseph@codesourcery.com>
Subject: Re: Last call for bikeshedding on attribute sym/exalias/reverse_alias
Date: Thu, 14 Sep 2023 07:01:44 -0300 [thread overview]
Message-ID: <ory1h9t6nr.fsf@lxoliva.fsfla.org> (raw)
In-Reply-To: <CAH6eHdQ3vT3MjohuE-izto+K=BMRykY3T-UyWa5-=OTDPM-JsQ@mail.gmail.com> (Jonathan Wakely's message of "Fri, 8 Sep 2023 09:32:47 +0100")
On Sep 8, 2023, Jonathan Wakely <jwakely.gcc@gmail.com> wrote:
> I think "symname" or "symalias" would be better than just "sym".
Thanks, I like symalias.
Does any object to it?
> Have you contacted anybody in the llvm community to see if they would
> implement it, or maybe already have something similar by another name?
I haven't, but there's nothing like it there.
--
Alexandre Oliva, happy hacker https://FSFLA.org/blogs/lxo/
Free Software Activist GNU Toolchain Engineer
More tolerance and less prejudice are key for inclusion and diversity
Excluding neuro-others for not behaving ""normal"" is *not* inclusive
prev parent reply other threads:[~2023-09-14 10:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <or365aghwf.fsf@livre.home>
[not found] ` <orzh7673v4.fsf@livre.home>
[not found] ` <ory1ji6ky5.fsf_-_@lxoliva.fsfla.org>
[not found] ` <e4d300a4-d84a-556b-d94f-904047ab5120@acm.org>
[not found] ` <orh6q13ks2.fsf@lxoliva.fsfla.org>
[not found] ` <CAFiYyc0TwLXgSUvFYp1BWkN-MvTTcwqHCj7YSybQrzaUn3=LYA@mail.gmail.com>
[not found] ` <orwmyvzece.fsf_-_@lxoliva.fsfla.org>
2023-09-08 5:25 ` Alexandre Oliva
2023-09-08 6:01 ` Dave Blanchard
2023-09-08 7:34 ` Jonathan Wakely
2023-09-08 8:32 ` Jonathan Wakely
2023-09-08 8:46 ` Roy Jacobson
2023-09-14 10:01 ` Alexandre Oliva [this message]
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=ory1h9t6nr.fsf@lxoliva.fsfla.org \
--to=oliva@adacore.com \
--cc=ebotcazou@adacore.com \
--cc=gcc@gcc.gnu.org \
--cc=hubicka@ucw.cz \
--cc=joseph@codesourcery.com \
--cc=jwakely.gcc@gmail.com \
--cc=nathan@acm.org \
/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).