public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/111705] New: [14 Regression] use of concepted copy constructored struct inside a template function messes up
Date: Thu, 05 Oct 2023 14:27:06 +0000	[thread overview]
Message-ID: <bug-111705-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 111705
           Summary: [14 Regression] use of concepted copy constructored
                    struct inside a template function messes up
           Product: gcc
           Version: 14.0
            Status: UNCONFIRMED
          Keywords: rejects-valid
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: pinskia at gcc dot gnu.org
  Target Milestone: ---

Take:
```
template<class> concept c = true;
template<class T>
struct ts
{
  template<class T1>
   requires(c<T1>)
    ts(const ts<T1>&);
  template<class T1>
   requires(!c<T1>)
    ts(const ts<T1>&) = delete;
  ts() = default;
};


using P = ts<int>;
void (*f)(P);
template<class>
void f1()
{  
  P x;
  f(x);
}
```
This gets rejected with the following (bogus) error message:
```
<source>: In substitution of 'template<class T1>  requires !(c<T1>)
ts<int>::ts(const ts<T1>&) [with T1 = int]':
<source>:21:5:   required from here
   21 |   f(x);
      |     ^
<source>:10:3:   required by the constraints of 'template<class T>
template<class T1>  requires !(c<T1>) ts<T>::ts(const ts<T1>&)'
<source>:9:12: error: satisfaction value of atomic constraint '!(c<T1>) [with
T1 = int]' changed from '<expression error>' to 'false'
    9 |   requires(!c<T1>)
      |           ~^~~~~~~
<source>:21:5: note: satisfaction value first evaluated to '<expression error>'
from here
   21 |   f(x);
      |     ^
```

This was reduced from PR 111703 (but is different since this was accepted
before  in GCC 13)

             reply	other threads:[~2023-10-05 14:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-05 14:27 pinskia at gcc dot gnu.org [this message]
2023-10-05 14:27 ` [Bug c++/111705] " pinskia at gcc dot gnu.org
2023-10-05 14:28 ` [Bug c++/111705] use of concepted copy constructored struct inside a template function messes up with -fchecking=2 pinskia at gcc dot gnu.org
2023-10-05 14:29 ` pinskia at gcc dot gnu.org
2023-10-05 14:29 ` [Bug c++/111705] [13/14 Regression] " pinskia at gcc dot gnu.org
2023-10-05 14:30 ` [Bug c++/111705] [12/13/14 " pinskia at gcc dot gnu.org
2023-11-16 17:37 ` [Bug c++/111705] [12/13 " ppalka at gcc dot gnu.org
2023-11-27 22:03 ` 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-111705-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).