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++/111703] [11/12/13 Regression] [C++20]Compiler fails when using generic lambda in specific situation since r11-550-gf65a3299a521a4 Date: Mon, 27 Nov 2023 22:02:51 +0000 [thread overview] Message-ID: <bug-111703-4-LAI14SyKBi@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111703-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111703 --- Comment #11 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-12 branch has been updated by Patrick Palka <ppalka@gcc.gnu.org>: https://gcc.gnu.org/g:c9cb7e3d75d494a6591887a99d0d3f7f7a307b2e commit r12-10017-gc9cb7e3d75d494a6591887a99d0d3f7f7a307b2e Author: Patrick Palka <ppalka@redhat.com> Date: Thu Nov 16 09:32:07 2023 -0500 c++: constantness of call to function pointer [PR111703] potential_constant_expression for CALL_EXPR tests FUNCTION_POINTER_TYPE_P on the callee rather than on the type of the callee, which means we always pass want_rval=any when recursing and so may fail to identify a non-constant function pointer callee as such. Fixing this turns out to further work around PR111703. PR c++/111703 PR c++/107939 gcc/cp/ChangeLog: * constexpr.cc (potential_constant_expression_1) <case CALL_EXPR>: Fix FUNCTION_POINTER_TYPE_P test. gcc/testsuite/ChangeLog: * g++.dg/cpp2a/concepts-fn8.C: Extend test. * g++.dg/diagnostic/constexpr4.C: New test. (cherry picked from commit 0077c0fb19981c108a01cd15af9b2d6d478c183b)
prev parent reply other threads:[~2023-11-27 22:02 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-05 12:40 [Bug c++/111703] New: [C++20]Compiler fails when using generic lambda in specific situation watanabemakoto.math at gmail dot com 2023-10-05 14:33 ` [Bug c++/111703] [12/13/14 Regression] " pinskia at gcc dot gnu.org 2023-10-05 14:36 ` pinskia at gcc dot gnu.org 2023-10-05 23:43 ` pinskia at gcc dot gnu.org 2023-10-27 23:40 ` ppalka at gcc dot gnu.org 2023-10-31 17:36 ` [Bug c++/111703] [11/12/13/14 Regression] [C++20]Compiler fails when using generic lambda in specific situation since r11-550-gf65a3299a521a4 ppalka at gcc dot gnu.org 2023-11-15 17:03 ` cvs-commit at gcc dot gnu.org 2023-11-16 14:32 ` cvs-commit at gcc dot gnu.org 2023-11-16 17:27 ` [Bug c++/111703] [11/12/13 " ppalka at gcc dot gnu.org 2023-11-24 16:56 ` cvs-commit at gcc dot gnu.org 2023-11-24 16:56 ` cvs-commit at gcc dot gnu.org 2023-11-27 22:02 ` cvs-commit at gcc dot gnu.org 2023-11-27 22:02 ` cvs-commit 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-111703-4-LAI14SyKBi@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).