public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Patrick Palka <ppalka@redhat.com>
To: Nathan Sidwell <nathan@acm.org>
Cc: Jason Merrill <jason@redhat.com>,
	Marek Polacek <polacek@redhat.com>,
	 Patrick Palka <ppalka@redhat.com>,
	GCC Patches <gcc-patches@gcc.gnu.org>
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)
In-Reply-To: <b17353a4-11be-0ff4-53d1-ed34c82d78f4@acm.org>

On Fri, 30 Sep 2022, Nathan Sidwell wrote:

> Hi,
> 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
> -- 
> Nathan Sidwell
> 
> 


      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]

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=78a4a509-1736-2aa4-6efa-ea51cadec5db@idea \
    --to=ppalka@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jason@redhat.com \
    --cc=nathan@acm.org \
    --cc=polacek@redhat.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).