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++/105996] [10/11 Regression] reinterpret_cast in constexpr failure creating a pair with a function pointer of class parent Date: Sat, 22 Apr 2023 00:23:09 +0000 [thread overview] Message-ID: <bug-105996-4-FtWgad8dg7@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105996-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105996 --- Comment #8 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-11 branch has been updated by Jason Merrill <jason@gcc.gnu.org>: https://gcc.gnu.org/g:b6c8048cdd2c1e523f663f248ba39caed5af90e7 commit r11-10646-gb6c8048cdd2c1e523f663f248ba39caed5af90e7 Author: Jason Merrill <jason@redhat.com> Date: Thu Mar 23 16:50:09 2023 -0400 c++: constexpr PMF conversion [PR105996] Here, we were calling build_reinterpret_cast regardless of whether there was actually a cast, and that now sets REINTERPRET_CAST_P. But that optimization seems dodgy anyway, as it involves NOP_EXPR from one RECORD_TYPE to another and we try to reserve NOP_EXPR for fundamental types. And the generated code seems the same, so let's drop it. And also strip location wrappers. PR c++/105996 gcc/cp/ChangeLog: * typeck.c (build_ptrmemfunc): Drop 0-offset optimization and location wrappers. gcc/testsuite/ChangeLog: * g++.dg/cpp0x/constexpr-pmf3.C: New test.
next prev parent reply other threads:[~2023-04-22 0:23 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-06-16 8:40 [Bug c++/105996] New: " jdapena at igalia dot com 2022-06-16 11:02 ` [Bug c++/105996] [12/11/12/13 Regression] " redi at gcc dot gnu.org 2022-06-16 15:36 ` [Bug c++/105996] [10/11/12/13 " jakub at gcc dot gnu.org 2022-06-16 15:39 ` jakub at gcc dot gnu.org 2022-06-20 9:49 ` rguenth at gcc dot gnu.org 2022-06-28 10:49 ` jakub at gcc dot gnu.org 2023-03-23 20:55 ` jason at gcc dot gnu.org 2023-03-23 21:39 ` cvs-commit at gcc dot gnu.org 2023-04-18 20:46 ` [Bug c++/105996] [10/11/12 " cvs-commit at gcc dot gnu.org 2023-04-21 20:28 ` [Bug c++/105996] [10/11 " cvs-commit at gcc dot gnu.org 2023-04-22 0:23 ` cvs-commit at gcc dot gnu.org [this message] 2023-07-07 10:43 ` [Bug c++/105996] [11 " rguenth at gcc dot gnu.org 2023-11-09 19:54 ` 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-105996-4-FtWgad8dg7@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).