public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ed at catmur dot uk" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/111602] New: "Error: symbol is already defined" for variable template dependent on default argument lambda used in sfinae and non-sfinae Date: Tue, 26 Sep 2023 17:15:39 +0000 [thread overview] Message-ID: <bug-111602-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111602 Bug ID: 111602 Summary: "Error: symbol is already defined" for variable template dependent on default argument lambda used in sfinae and non-sfinae Product: gcc Version: 14.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: ed at catmur dot uk Target Milestone: --- Since gcc 8.1, template<class> constexpr bool V = true; struct F { template<class T, bool = V<T>> F(T) {} }; template<class T> struct C { C(F = []{}) {} }; template<class T> decltype(T()) g() { return T(); } auto f() { struct T {} t; return t; }; int main() { g<C<decltype(f())>>(); } compiled at -O0 (and -std=c++14 or above) causes assembler error: /tmp/cccVZwwU.s: Assembler messages: /tmp/cccVZwwU.s:106: Error: symbol `_Z1VIZN1CIZ1fvE1TEC4E1FEd_UlvE_E' is already defined The symbol demangles as 'V<C<f()::T>::C(F)::{default arg#1}::{lambda()#1}>'.
next reply other threads:[~2023-09-26 17:15 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-09-26 17:15 ed at catmur dot uk [this message] 2023-09-26 17:22 ` [Bug c++/111602] "Error: symbol is already defined" for variable template dependent on default argument lambda of class dependent on local type used in sfinae and non-sfinae contexts pinskia at gcc dot gnu.org 2023-09-26 17:23 ` [Bug c++/111602] [11/12/13/14 Regression] " pinskia at gcc dot gnu.org 2023-09-26 19:33 ` ed at catmur dot uk 2023-10-25 20:15 ` ppalka at gcc dot gnu.org 2024-07-19 13:21 ` [Bug c++/111602] [12/13/14/15 " rguenth 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-111602-4@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).