public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/41226] [4.5 regression] Revision 151313 caused many regressions on trunk
Date: Wed, 02 Sep 2009 14:39:00 -0000	[thread overview]
Message-ID: <20090902143911.17215.qmail@sourceware.org> (raw)
In-Reply-To: <bug-41226-682@http.gcc.gnu.org/bugzilla/>



------- Comment #2 from joseph at codesourcery dot com  2009-09-02 14:39 -------
Subject: Re:  [4.5 regression] Revision 151313 caused many
 regressions on trunk

On Wed, 2 Sep 2009, jakub at gcc dot gnu dot org wrote:

> Only pr40753.c is a regression, the rest are new tests.  And guality tests are
> very much expected to FAIL when -fvar-tracking-assignments isn't enabled (to be
> enabled in SVN today), or if you don't have very latest gdb.

There is a difference between expected to fail on execution and expected 
to fail to compile.  This bug report is reporting that they are failing to 
compile, and it's only execution that's XFAILed.  What are the "excess 
errors" in the log?


-- 


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


  parent reply	other threads:[~2009-09-02 14:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-02 14:09 [Bug debug/41226] New: " hjl dot tools at gmail dot com
2009-09-02 14:18 ` [Bug debug/41226] " rguenth at gcc dot gnu dot org
2009-09-02 14:19 ` jakub at gcc dot gnu dot org
2009-09-02 14:39 ` joseph at codesourcery dot com [this message]
2009-09-03  5:35 ` aoliva at gcc dot gnu dot org
2009-09-04 19:10 ` aoliva at gcc dot gnu dot 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=20090902143911.17215.qmail@sourceware.org \
    --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).