public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc(refs/vendors/redhat/heads/gcc-8-branch)] testsuite: Adjust expected error in a testcase [PR98358] Date: Fri, 14 May 2021 14:55:46 +0000 (GMT) [thread overview] Message-ID: <20210514145546.CC05A3949F32@sourceware.org> (raw) https://gcc.gnu.org/g:27b3e1e11d3f1cc7a2994bb9d143a1a02d8c51c3 commit 27b3e1e11d3f1cc7a2994bb9d143a1a02d8c51c3 Author: Jakub Jelinek <jakub@redhat.com> Date: Fri Apr 30 15:17:31 2021 +0200 testsuite: Adjust expected error in a testcase [PR98358] On Fri, Apr 23, 2021 at 05:24:00PM -0400, Jason Merrill via Gcc wrote: > > We have one P1 bug though - P98358 - it is unclear if just changing the > > testcase is all that is needed or if some C++ FE changes are needed. > > The error message quoted in the PR looks correct, so I think changing > the testcase is sufficient. 2021-04-30 Jakub Jelinek <jakub@redhat.com> PR c++/98358 * g++.dg/template/pr98297.C: Expect error about shadowing template template parameter rather than does not declare anything error. Diff: --- gcc/testsuite/g++.dg/template/pr98297.C | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/gcc/testsuite/g++.dg/template/pr98297.C b/gcc/testsuite/g++.dg/template/pr98297.C index 0dd63a57b5c..9e7d07e2c18 100644 --- a/gcc/testsuite/g++.dg/template/pr98297.C +++ b/gcc/testsuite/g++.dg/template/pr98297.C @@ -2,5 +2,5 @@ // { dg-do compile { target c++11 } } template <template <class> class a> struct [[b]] -a <int>; // { dg-error "does not declare anything" } +a <int>; // { dg-error "name of class shadows template template parameter" } // { dg-warning "ignored" "" { target *-*-* } .-1 }
reply other threads:[~2021-05-14 14:55 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20210514145546.CC05A3949F32@sourceware.org \ --to=jakub@gcc.gnu.org \ --cc=gcc-cvs@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).