From: Patrick Palka <firstname.lastname@example.org>
To: Nathan Sidwell <email@example.com>
Cc: Jason Merrill <firstname.lastname@example.org>,
Marek Polacek <email@example.com>,
Patrick Palka <firstname.lastname@example.org>,
GCC Patches <email@example.com>
Subject: Re: C++ ABI
Date: Fri, 30 Sep 2022 12:32:13 -0400 (EDT) [thread overview]
Message-ID: <78a4a509-1736-2aa4-6efa-ea51cadec5db@idea> (raw)
On Fri, 30 Sep 2022, Nathan Sidwell wrote:
> I've discovered some mangling problems with lambdas. (a) divergence from
> clang and (b) manglings that incorrectly demangle. With #a I'm not yet sure
> who is correct. for #b g++ is definitely wrong.
> From the docs, it doesn't appear to have been bumped this cycle. Is that
> correct, and I should bump it to 18?
AFAICT it hasn't been bumped since no mangling changes have been made
yet this cycle.
> Nathan Sidwell
prev parent reply other threads:[~2022-09-30 16:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-30 13:43 Nathan Sidwell
2022-09-30 13:54 ` Nathan Sidwell
2022-09-30 16:32 ` Patrick Palka [this message]
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).