public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/107897] [13 Regression] mangling conflicts with a previous mangle since r13-3601
Date: Thu, 02 Feb 2023 16:12:59 +0000 [thread overview]
Message-ID: <bug-107897-4-YYMNlsnrRz@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107897-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107897
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jason at gcc dot gnu.org
--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
The error can be certainly worked around with -fabi-compat-version=18, but I
wonder
if we just shouldn't disable mangling aliases for decls where
write_closure_type_name
has been called and LAMBDA_EXPR_SCOPE_SIG_DISCRIMINATOR !=
LAMBDA_EXPR_SCOPE_ONLY_DISCRIMINATOR. Because the mangling change doesn't look
like mangle this differently, but use different numbering scheme in the same
mangling.
If yes, it could be arranged by
if ((LAMBDA_EXPR_SCOPE_SIG_DISCRIMINATOR (lambda)
!= LAMBDA_EXPR_SCOPE_ONLY_DISCRIMINATOR (lambda))
&& abi_warn_or_compat_version_crosses (18))
G.need_abi_warning = true;
not setting just the G.need_abi_warning flag but some new flag in G which would
disable creation of the mangling alias.
Thoughts on that?
next prev parent reply other threads:[~2023-02-02 16:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-28 17:56 [Bug c++/107897] New: [13 Regression] ICE in verify_curr_properties, at passes.cc:2201 gscfq@t-online.de
2022-11-28 18:06 ` [Bug c++/107897] " pinskia at gcc dot gnu.org
2022-11-29 7:43 ` rguenth at gcc dot gnu.org
2022-11-29 9:26 ` cvs-commit at gcc dot gnu.org
2022-11-29 9:27 ` [Bug c++/107897] [13 Regression] mangling conflicts with a previous mangle rguenth at gcc dot gnu.org
2022-12-01 15:39 ` [Bug c++/107897] [13 Regression] mangling conflicts with a previous mangle since r13-3601 jakub at gcc dot gnu.org
2022-12-21 9:53 ` rguenth at gcc dot gnu.org
2023-02-02 16:12 ` jakub at gcc dot gnu.org [this message]
2023-03-06 20:01 ` jason at gcc dot gnu.org
2023-03-09 21:59 ` jason at gcc dot gnu.org
2023-03-30 11:23 ` cvs-commit at gcc dot gnu.org
2023-03-30 12:13 ` jason at gcc dot gnu.org
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=bug-107897-4-YYMNlsnrRz@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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).