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++/103408] ICE when requires auto(x) in C++23
Date: Wed, 15 Dec 2021 10:20:59 +0000 [thread overview]
Message-ID: <bug-103408-4-rq7T0yXScD@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103408-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103408
--- Comment #8 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>:
https://gcc.gnu.org/g:6bf5d9108ae2dcb6cb883442d7bd299fd8fc15e9
commit r12-5995-g6bf5d9108ae2dcb6cb883442d7bd299fd8fc15e9
Author: Jakub Jelinek <jakub@redhat.com>
Date: Wed Dec 15 11:18:14 2021 +0100
testsuite: Fix up cpp23/auto-fncast11.C testcase [PR103408]
This test fails:
+FAIL: g++.dg/cpp23/auto-fncast11.C -std=c++2b (test for errors, line 19)
+FAIL: g++.dg/cpp23/auto-fncast11.C -std=c++2b (test for excess errors)
because the regex in dg-error was missing an indefinite article.
2021-12-15 Jakub Jelinek <jakub@redhat.com>
PR c++/103408
* g++.dg/cpp23/auto-fncast11.C: Fix expected diagnostic wording.
next prev parent reply other threads:[~2021-12-15 10:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-24 16:20 [Bug c++/103408] New: " hewillk at gmail dot com
2021-11-24 16:23 ` [Bug c++/103408] " mpolacek at gcc dot gnu.org
2021-11-24 16:24 ` mpolacek at gcc dot gnu.org
2021-11-25 13:38 ` hewillk at gmail dot com
2021-11-30 21:22 ` mpolacek at gcc dot gnu.org
2021-12-02 13:12 ` cvs-commit at gcc dot gnu.org
2021-12-06 13:59 ` ppalka at gcc dot gnu.org
2021-12-14 13:16 ` cvs-commit at gcc dot gnu.org
2021-12-15 10:20 ` cvs-commit at gcc dot gnu.org [this message]
2021-12-15 20:04 ` 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-103408-4-rq7T0yXScD@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).