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 tree-optimization/20605] [4.1 Regression] gcc.dg/tree-ssa/loop-4.c scan-tree-dump-times iter 0 fails
Date: Mon, 16 May 2005 20:05:00 -0000 [thread overview]
Message-ID: <20050516200552.1083.qmail@sourceware.org> (raw)
In-Reply-To: <20050323163529.20605.jsm28@gcc.gnu.org>
------- Additional Comments From joseph at codesourcery dot com 2005-05-16 20:05 -------
Subject: Re: [4.1 Regression] gcc.dg/tree-ssa/loop-4.c
scan-tree-dump-times iter 0 fails
On Mon, 16 May 2005, pinskia at gcc dot gnu dot org wrote:
> Or it might be the testcase which is matching it wrong, someone already asked about this testcase
> before on IRC (IIRC) and the regex was just matching wrongly.
No, that's bug 21341 (if indeed the problem was the regex, the submitter
of the patch which changed the regex didn't mention the bug and its prior
change from PASS to FAIL). There are multiple test assertions within the
same test file, and when any one changes from PASS to FAIL that is in
principle, and in practice in this case, a separate bug.
http://gcc.gnu.org/ml/gcc-patches/2005-05/msg01057.html
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20605
next prev parent reply other threads:[~2005-05-16 20:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-23 16:35 [Bug tree-optimization/20605] New: " jsm28 at gcc dot gnu dot org
2005-03-23 16:37 ` [Bug tree-optimization/20605] " jsm28 at gcc dot gnu dot org
2005-03-24 17:20 ` [Bug tree-optimization/20605] [4.1 Regression] " jsm28 at gcc dot gnu dot org
2005-03-31 2:29 ` danglin at gcc dot gnu dot org
2005-04-17 22:25 ` jsm28 at gcc dot gnu dot org
2005-04-17 23:07 ` pinskia at gcc dot gnu dot org
2005-05-16 19:53 ` pinskia at gcc dot gnu dot org
2005-05-16 20:05 ` joseph at codesourcery dot com [this message]
2005-09-01 20:27 ` jsm28 at gcc dot gnu dot org
2005-09-01 21:15 ` pinskia 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=20050516200552.1083.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).