public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/114393] [14 regression] over eager "invalid use of void expression" ? since r14-2170-g4cf64d9cc2faf4 Date: Wed, 20 Mar 2024 04:04:37 +0000 [thread overview] Message-ID: <bug-114393-4-GRlyyADetx@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114393-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114393 --- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Reduced testcase which shows this never worked: ``` template <auto _DescriptorFn> struct c1 {}; template <class _Descriptor, auto t = [] { return _Descriptor();}> inline constexpr auto b_v = t; template <class _Tag> using c1_t = c1<b_v<int>>; template <class _Data> constexpr auto g(_Data __data) { return c1_t<_Data>{}; } void f() { auto &&b = g(0); } ``` I don't know understand how the original testcase worked in GCC 13 when the above testcase never worked ...
next prev parent reply other threads:[~2024-03-20 4:04 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-19 11:09 [Bug c++/114393] New: over eager "invalid use of void expression" ? prlw1 at cam dot ac.uk 2024-03-19 11:29 ` [Bug c++/114393] [14 regression] " redi at gcc dot gnu.org 2024-03-19 11:32 ` redi at gcc dot gnu.org 2024-03-19 11:56 ` [Bug c++/114393] [14 regression] over eager "invalid use of void expression" ? since r14-2170-g4cf64d9cc2faf4 rguenth at gcc dot gnu.org 2024-03-19 22:42 ` pinskia at gcc dot gnu.org 2024-03-20 3:51 ` pinskia at gcc dot gnu.org 2024-03-20 4:04 ` pinskia at gcc dot gnu.org [this message] 2024-03-25 19:05 ` ppalka at gcc dot gnu.org 2024-03-29 23:49 ` law at gcc dot gnu.org 2024-04-12 19:08 ` ppalka at gcc dot gnu.org 2024-04-12 19:09 ` ppalka at gcc dot gnu.org 2024-04-12 19:11 ` ppalka at gcc dot gnu.org 2024-04-14 19:27 ` prlw1 at cam dot ac.uk
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-114393-4-GRlyyADetx@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).