public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "grosser at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/50023] FAIL: gcc.dg/graphite/id-pr46845.c (test for excess errors)
Date: Mon, 09 Jan 2012 19:21:00 -0000	[thread overview]
Message-ID: <bug-50023-4-sfyri0NWKv@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-50023-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50023

Tobias Grosser <grosser at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |FIXED

--- Comment #3 from Tobias Grosser <grosser at gcc dot gnu.org> 2012-01-09 19:20:13 UTC ---
(In reply to comment #2)
> A patch has been submitted at
> http://gcc.gnu.org/ml/gcc-patches/2011-10/msg00611.html and approved at
> http://gcc.gnu.org/ml/gcc-patches/2011-10/msg00612.html . Any reason why it has
> not been committed?

To me it seems it was committed 10.10.2011. Here the relevant commit:
http://gcc.gnu.org/viewcvs?view=revision&revision=179762

Does this commit not show up for you?

I marked this as resolved. If you cannot find the commit, please reopen the
bug.

All the best from ENS Paris
Tobi


  parent reply	other threads:[~2012-01-09 19:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-08 13:17 [Bug testsuite/50023] New: " dominiq at lps dot ens.fr
2011-09-04 13:28 ` [Bug testsuite/50023] " dominiq at lps dot ens.fr
2012-01-08 16:24 ` dominiq at lps dot ens.fr
2012-01-09 19:21 ` grosser at gcc dot gnu.org [this message]
2012-01-09 21:13 ` dominiq at lps dot ens.fr

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-50023-4-sfyri0NWKv@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).