public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/105996] [10/11/12/13 Regression] reinterpret_cast in constexpr failure creating a pair with a function pointer of class parent Date: Thu, 16 Jun 2022 15:36:40 +0000 [thread overview] Message-ID: <bug-105996-4-J2zcxrqLoo@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 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jason at gcc dot gnu.org --- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> --- The problem is that build_ptrmemfunc in 9587 if (TREE_CODE (pfn) != PTRMEM_CST) 9588 { 9589 if (same_type_p (to_type, pfn_type)) 9590 return pfn; 9591 else if (integer_zerop (n) && TREE_CODE (pfn) != CONSTRUCTOR) 9592 return build_reinterpret_cast (input_location, to_type, pfn, 9593 complain); 9594 } calls build_reintepret_cast from void (A::*)() typed pfn to void (B::*)() type, and when we then constant expression evaluate it, we reject it because reinterpret_cast is not a core constant expression as per https://eel.is/c++draft/expr.const#5.16 Now, is this reinterpret cast just some implementation detail under the hood in which we should somehow arrange for REINTERPRET_CAST_P bit not be set (or afterwards remove it)?
next prev parent reply other threads:[~2022-06-16 15:36 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 ` jakub at gcc dot gnu.org [this message] 2022-06-16 15:39 ` [Bug c++/105996] [10/11/12/13 " 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 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-J2zcxrqLoo@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).