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:16 +0000 [thread overview] Message-ID: <bug-96830-4-20th8RS0cX@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 #13 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:cd5baeb4489b6a953abbc7f02fea457fd9ed2f83 commit r13-6677-gcd5baeb4489b6a953abbc7f02fea457fd9ed2f83 Author: Patrick Palka <ppalka@redhat.com> Date: Tue Mar 14 19:14:29 2023 -0400 c++: redeclaring member of constrained class template [PR96830] An out-of-line definition of a member of a constrained class template needs to repeat the template's constraints, but it turns out we don't verify anywhere that the two sets of constraints match. This patch adds such a check to push_template_decl, nearby a similar consistency check for the template parameter list lengths. PR c++/96830 gcc/cp/ChangeLog: * pt.cc (push_inline_template_parms_recursive): Set TEMPLATE_PARMS_CONSTRAINTS. (push_template_decl): For an out-of-line declaration, verify constraints for each enclosing template scope match those of the original template declaratation. gcc/testsuite/ChangeLog: * g++.dg/cpp2a/concepts-class5.C: New test. * g++.dg/cpp2a/concepts-class5a.C: New test.
next prev 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 2023-03-14 23:18 ` cvs-commit at gcc dot gnu.org [this message] 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-20th8RS0cX@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: linkBe 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).