public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/105996] [12/11/12/13 Regression] reinterpret_cast in constexpr failure creating a pair with a function pointer of class parent
Date: Thu, 16 Jun 2022 11:02:36 +0000	[thread overview]
Message-ID: <bug-105996-4-e9HvzkmKaz@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

Jonathan Wakely <redi at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|reinterpret_cast in         |[12/11/12/13 Regression]
                   |constexpr failure creating  |reinterpret_cast in
                   |a pair with a function      |constexpr failure creating
                   |pointer of class parent     |a pair with a function
                   |                            |pointer of class parent
   Last reconfirmed|                            |2022-06-16
             Status|UNCONFIRMED                 |NEW
     Ever confirmed|0                           |1
      Known to fail|                            |10.3.0, 11.3.0, 12.1.0,
                   |                            |13.0, 8.1.0
                 CC|                            |jakub at gcc dot gnu.org
      Known to work|                            |7.5.0

--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Reduced:

template<typename T, typename U> constexpr int make_pair(T&&, U&&) { return 0;
}

struct A {
  void CB() {}
};

struct B : public A {
  void Test() {
  using MyCB = void (B::*)();
  static constexpr auto p = make_pair<int, MyCB>(1, &B::CB);
  }
};


105996.C: In member function 'void B::Test()':
105996.C:10:53: error: a reinterpret_cast is not a constant expression
   static constexpr auto p = make_pair<int, MyCB>(1, &B::CB);
                                                     ^~
Started to fail some time before r256448, probably 


commit e99ef40892b598eeb3fa496cc472e111675d7f6c
Author: Jakub Jelinek 
Date:   Wed Jan 10 16:59:09 2018

    re PR c++/81327 (cast to void* does not suppress -Wclass-memaccess)

            PR c++/81327
            * call.c (maybe_warn_class_memaccess): Add forward declaration.
            Change last argument from tree * to const vec<tree, va_gc> *,
adjust
            args uses and check number of operands too.  Don't strip away any
            nops.  Use maybe_constant_value when looking for INTEGER_CST args.
            Deal with src argument not having pointer type.  Check
            tree_fits_uhwi_p before calling tree_to_uhwi.  Remove useless
            test.
            (build_over_call): Call maybe_warn_class_memaccess here on the
            original arguments.
            (build_cxx_call): Rather than here on converted arguments.

            * g++.dg/Wclass-memaccess-2.C: Don't expect a warning when
explicitly
            cast to void *.

    From-SVN: r256440

  reply	other threads:[~2022-06-16 11:02 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 ` redi at gcc dot gnu.org [this message]
2022-06-16 15:36 ` [Bug c++/105996] [10/11/12/13 Regression] " 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
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-e9HvzkmKaz@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: link
Be 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).