From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Jason Merrill <jason@redhat.com>
Cc: gcc-patches List <gcc-patches@gcc.gnu.org>
Subject: Re: v3 testsuite PATCH to avoid dg-excess-errors
Date: Fri, 10 Jun 2011 08:56:00 -0000 [thread overview]
Message-ID: <BANLkTink2g=WRKr5sT+_486DMnreUo6KSw@mail.gmail.com> (raw)
In-Reply-To: <4DF19363.6030309@redhat.com>
On 10 June 2011 04:45, Jason Merrill wrote:
>
> Doing this revealed that the bind/ref_neg.cc test was broken; the dg-error
> tags were missing a space before the closing }, so they were being ignored.
> When I fix that, I find that two of the tests are failing.
Doh.
> I'm committing the first patch, but am holding off on the second for now.
> Should I go ahead and commit it or would someone like to fix those bugs and
> then commit it themselves?
I'll look at the broken tests asap, but that will be after work in
about 8 hours. I'm ok if you want to go ahead and commit the patch,
but if you do let's warn HJ that the regression testers will see the
FAILs.
next prev parent reply other threads:[~2011-06-10 8:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-10 4:46 Jason Merrill
2011-06-10 8:56 ` Jonathan Wakely [this message]
2011-06-10 12:12 ` Paolo Carlini
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='BANLkTink2g=WRKr5sT+_486DMnreUo6KSw@mail.gmail.com' \
--to=jwakely.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--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).