public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "oliver.rosten at googlemail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/104410] New: Internal error using default-initialized constexpr bool in requires clause
Date: Sun, 06 Feb 2022 17:20:43 +0000	[thread overview]
Message-ID: <bug-104410-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104410

            Bug ID: 104410
           Summary: Internal error using default-initialized constexpr
                    bool in requires clause
           Product: gcc
           Version: 11.2.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: oliver.rosten at googlemail dot com
  Target Milestone: ---

#include <type_traits>

template<class T>
constexpr bool use_func_v{};

// Using this instead is fine!
//template<class T>
//constexpr bool use_func_v{false};

struct func_obj
{
    template<class T>
        requires use_func_v<T>
    void operator()(T, T) const
    {}
};

constexpr bool bar{std::is_invocable_v<func_obj, char, char>};

----> internal error, see

https://godbolt.org/z/qsbPYq67a

             reply	other threads:[~2022-02-06 17:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-06 17:20 oliver.rosten at googlemail dot com [this message]
2022-02-06 23:36 ` [Bug c++/104410] [11/12 Regression] " pinskia at gcc dot gnu.org
2022-02-06 23:39 ` pinskia at gcc dot gnu.org
2022-02-06 23:53 ` pinskia at gcc dot gnu.org
2022-02-07  8:56 ` rguenth at gcc dot gnu.org
2022-02-07 14:31 ` ppalka at gcc dot gnu.org
2022-02-08 14:12 ` cvs-commit at gcc dot gnu.org
2022-02-08 14:13 ` [Bug c++/104410] [11 " ppalka at gcc dot gnu.org
2022-02-08 17:33 ` cvs-commit at gcc dot gnu.org
2022-02-08 17:58 ` 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-104410-4@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).