public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/111300] Modules error: mangling of [lambda] conflicts with previous mangle Date: Sun, 10 Sep 2023 09:24:42 +0000 [thread overview] Message-ID: <bug-111300-4-7VSr4SZ4Fg@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111300-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111300 --- Comment #7 from Jonathan Wakely <redi at gcc dot gnu.org> --- Given the note, maybe this is an intentional error to avoid creating a compiled module interface that might not be usable: note: a later '-fabi-version=' (or =0) avoids this error with a change in mangling But since a compiled module can't be used with different versions of the compiler or even with different flags, I'm not sure how any conflict can happen.
prev parent reply other threads:[~2023-09-10 9:24 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-09-06 2:44 [Bug c++/111300] New: [14 Regression] g++.dg/modules/xtreme-header-2_b.C hp at gcc dot gnu.org 2023-09-06 13:40 ` [Bug c++/111300] [14 Regression] g++.dg/modules/xtreme-header_b.C redi at gcc dot gnu.org 2023-09-09 13:37 ` redi at gcc dot gnu.org 2023-09-09 19:58 ` redi at gcc dot gnu.org 2023-09-09 21:39 ` hp at gcc dot gnu.org 2023-09-09 21:41 ` hp at gcc dot gnu.org 2023-09-10 9:15 ` [Bug c++/111300] Modules error: mangling of [lambda] conflicts with previous mangle redi at gcc dot gnu.org 2023-09-10 9:24 ` redi at gcc dot gnu.org [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=bug-111300-4-7VSr4SZ4Fg@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: linkBe 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).