public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/105386] [11 Regression] Tuple in unevaluated context is instantiated; creates reference to void Date: Thu, 28 Apr 2022 15:39:40 +0000 [thread overview] Message-ID: <bug-105386-4-4hKJO2p10a@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105386-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105386 --- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-11 branch has been updated by Patrick Palka <ppalka@gcc.gnu.org>: https://gcc.gnu.org/g:8969d00bf16a8f4de79306010fca8f14f91c171d commit r11-9947-g8969d00bf16a8f4de79306010fca8f14f91c171d Author: Patrick Palka <ppalka@redhat.com> Date: Tue Apr 26 10:53:38 2022 -0400 c++: decltype of non-dependent call of class type [PR105386] We need to pass tf_decltype when instantiating a non-dependent decltype operand, like tsubst does in the dependent case, so that we don't force completion of a prvalue operand's class type. PR c++/105386 gcc/cp/ChangeLog: * semantics.c (finish_decltype_type): Pass tf_decltype to instantiate_non_dependent_expr_sfinae. gcc/testsuite/ChangeLog: * g++.dg/cpp0x/decltype81.C: New test. (cherry picked from commit b6a48401da51e9042b6f0822d532b3b472492658)
next prev parent reply other threads:[~2022-04-28 15:39 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-26 0:31 [Bug c++/105386] New: " cuzdav at gmail dot com 2022-04-26 6:59 ` [Bug c++/105386] [11/12 Regression] " rguenth at gcc dot gnu.org 2022-04-26 9:30 ` jakub at gcc dot gnu.org 2022-04-26 12:19 ` ppalka at gcc dot gnu.org 2022-04-26 14:54 ` cvs-commit at gcc dot gnu.org 2022-04-26 15:20 ` [Bug c++/105386] [11 " ppalka at gcc dot gnu.org 2022-04-28 15:39 ` cvs-commit at gcc dot gnu.org [this message] 2022-04-28 15:40 ` ppalka 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-105386-4-4hKJO2p10a@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).