public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "xinliangli at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/49261] [4.7 Regression] FAIL: gcc.dg/tree-ssa/forwprop-9.c
Date: Wed, 01 Jun 2011 22:28:00 -0000 [thread overview]
Message-ID: <bug-49261-4-5hjNK31rdc@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-49261-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49261
davidxl <xinliangli at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |xinliangli at gmail dot com
--- Comment #1 from davidxl <xinliangli at gmail dot com> 2011-06-01 22:27:59 UTC ---
(In reply to comment #0)
> On Linux/ia32, revision 174538 gave
>
> FAIL: gcc.dg/tree-ssa/forwprop-9.c scan-tree-dump-times optimized " = 1" 2
>
> Revision 174535 is OK.
Right -- the counting of '= 1' is screwed up.
David
next prev parent reply other threads:[~2011-06-01 22:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-01 19:13 [Bug middle-end/49261] New: " hjl.tools at gmail dot com
2011-06-01 19:35 ` [Bug middle-end/49261] " rguenth at gcc dot gnu.org
2011-06-01 22:28 ` xinliangli at gmail dot com [this message]
2011-06-02 9:44 ` rguenth at gcc dot gnu.org
2011-06-02 16:34 ` xinliangli at gmail dot com
2011-06-03 13:05 ` jakub at gcc dot gnu.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=bug-49261-4-5hjNK31rdc@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).