public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "src at andyf dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/96745] New: [concepts] internal compiler error: in type_memfn_rqual, at cp/typeck.c:10389
Date: Sat, 22 Aug 2020 12:47:00 +0000	[thread overview]
Message-ID: <bug-96745-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 96745
           Summary: [concepts] internal compiler error: in
                    type_memfn_rqual, at cp/typeck.c:10389
           Product: gcc
           Version: 10.2.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: src at andyf dot de
  Target Milestone: ---

Hello,

the following code gives an internal compiler error.

template<typename T>
struct Test {
    ~Test() requires true {}
    ~Test() requires true && true {}
};

Test<int> t;


Error:
<source>: In instantiation of 'struct Test<int>':
<source>:7:11:   required from here
<source>:2:8: internal compiler error: in type_memfn_rqual, at
cp/typeck.c:10389
    2 | struct Test {
      |        ^~~~
Please submit a full bug report,
with preprocessed source if appropriate.
See <https://gcc.gnu.org/bugs/> for instructions.
Compiler returned: 1



The code is ill-formed, the compiler cannot identify which of the two
destructors is the most constrained. However, I think a more helpful error
message would assist me in a large code-base much more.

Live: https://godbolt.org/z/6dP8PG



Andreas

             reply	other threads:[~2020-08-22 12:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-22 12:47 src at andyf dot de [this message]
2020-09-22 19:34 ` [Bug c++/96745] " ppalka at gcc dot gnu.org
2021-01-17 16:52 ` ppalka at gcc dot gnu.org
2021-01-17 16:57 ` ppalka at gcc dot gnu.org
2021-05-05 16:30 ` ppalka at gcc dot gnu.org
2021-09-07 20:43 ` pinskia at gcc dot gnu.org
2023-01-30 20:36 ` ppalka at gcc dot gnu.org
2023-02-03 14:15 ` cvs-commit at gcc dot gnu.org
2023-02-03 14:21 ` ppalka at gcc dot gnu.org
2023-02-03 14:23 ` 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-96745-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).