public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Dave Blanchard <dave@killthe.net>
To: gcc@gcc.gnu.org
Cc: Alexandre Oliva <oliva@adacore.com>
Subject: Re: Last call for bikeshedding on attribute sym/exalias/reverse_alias
Date: Fri, 8 Sep 2023 01:01:09 -0500	[thread overview]
Message-ID: <20230908010109.d44b38afbf1381466fbcc8ee@killthe.net> (raw)
In-Reply-To: <orpm2tgrsd.fsf_-_@lxoliva.fsfla.org>

On Fri, 08 Sep 2023 02:25:38 -0300
Alexandre Oliva via Gcc <gcc@gcc.gnu.org> wrote:

> Attribute sym, named after symver, is the one in the latest version of
> the patch.  mnemonic_alias, convenience_alias and asm_alias are other
> possibilities that comes to mind.  The 2020-August thread has many more.

Sounds like a useful feature. Since it specifically deals with C++ name mangling, how about 'demangle'?

C++ is an abomination and name mangling is a perfect example of the brain damage surrounding this abortion of a language, but I digress...

  reply	other threads:[~2023-09-08  5:58 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 [this message]
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

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=20230908010109.d44b38afbf1381466fbcc8ee@killthe.net \
    --to=dave@killthe.net \
    --cc=gcc@gcc.gnu.org \
    --cc=oliva@adacore.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).