From: Marek Polacek <polacek@redhat.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Jason Merrill <jason@redhat.com>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Fix P0634R3 - Down with typename! testsuite fallout
Date: Tue, 04 Dec 2018 13:19:00 -0000 [thread overview]
Message-ID: <20181204131923.GH21364@redhat.com> (raw)
In-Reply-To: <20181204084251.GF12380@tucnak>
On Tue, Dec 04, 2018 at 09:42:51AM +0100, Jakub Jelinek wrote:
> Hi!
>
> I've noticed these two tests now FAIL with -std=c++2a, they don't print
> any diagnostics. As I believe that was the point of the P0634R3 changes,
> this patch adjusts the testcases. Tested on x86_64-linux, ok for trunk?
>
> 2018-12-04 Jakub Jelinek <jakub@redhat.com>
>
> * g++.old-deja/g++.oliva/typename1.C: Don't expect any diagnostics
> for C++2a.
> * g++.old-deja/g++.oliva/typename2.C: Likewise.
The patch is fine, sorry for missing that. Apparently I only ran c++2a
with dg.exp.
Marek
prev parent reply other threads:[~2018-12-04 13:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-04 8:43 Jakub Jelinek
2018-12-04 13:19 ` Marek Polacek [this message]
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=20181204131923.GH21364@redhat.com \
--to=polacek@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=jason@redhat.com \
/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).