public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/96830] GCC does not complain about redeclaration with inconsistent requires clause
Date: Tue, 14 Mar 2023 23:18:11 +0000	[thread overview]
Message-ID: <bug-96830-4-s0TMVA9MR6@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96830-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #12 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Patrick Palka <ppalka@gcc.gnu.org>:

https://gcc.gnu.org/g:ec62dc95c4f8776c9f4eff2a9a06f9aef6a2d98a

commit r13-6676-gec62dc95c4f8776c9f4eff2a9a06f9aef6a2d98a
Author: Patrick Palka <ppalka@redhat.com>
Date:   Tue Mar 14 19:12:08 2023 -0400

    c++: constrained template friend class matching [PR96830]

    When instantiating a constrained template friend naming an already
    declared class template, tsubst_friend_class erroneously passes to
    redeclare_class_template the existing template's constraints instead of
    those of the friend declaration, which causes the constraint comparison
    check therein to trivially succeed and we fail to diagnose legitimate
    constraint mismatches.

            PR c++/96830

    gcc/cp/ChangeLog:

            * pt.cc (redeclare_class_template): Add missing "of" in
            constraint mismatch diagnostic.
            (tsubst_friend_class): For an already declared class template,
            substitute and pass the friend declaration's constraints to
            redeclare_class_template instead of passing the existing
            template's constraints.

    gcc/testsuite/ChangeLog:

            * g++.dg/cpp2a/concepts-friend14.C: New test.

  parent reply	other threads:[~2023-03-14 23:18 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-28  8:39 [Bug c++/96830] New: GCC does not complain template-head containing " p.hyundeok76 at gmail dot com
2020-08-28 11:13 ` [Bug c++/96830] " redi at gcc dot gnu.org
2020-08-28 11:24 ` redi at gcc dot gnu.org
2020-08-28 11:26 ` redi at gcc dot gnu.org
2022-07-20  9:54 ` redi at gcc dot gnu.org
2022-07-20 22:59 ` [Bug c++/96830] GCC does not complain about redeclaration with inconsistent " cvs-commit at gcc dot gnu.org
2022-07-21 11:17 ` cvs-commit at gcc dot gnu.org
2022-07-22  7:07 ` cvs-commit at gcc dot gnu.org
2022-10-02  6:59 ` oschonrock at gmail dot com
2022-10-02 18:43 ` redi at gcc dot gnu.org
2022-10-02 18:46 ` redi at gcc dot gnu.org
2022-10-03 13:58 ` redi at gcc dot gnu.org
2022-10-31 16:57 ` ppalka at gcc dot gnu.org
2023-03-13 20:40 ` ppalka at gcc dot gnu.org
2023-03-14 23:18 ` cvs-commit at gcc dot gnu.org [this message]
2023-03-14 23:18 ` cvs-commit at gcc dot gnu.org
2023-03-14 23:28 ` ppalka at gcc dot gnu.org
2023-04-27 23:04 ` cvs-commit 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-96830-4-s0TMVA9MR6@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).