public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dave.anglin at bell dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/60707] FAIL: gfortran.dg/pr45636.f90 -O scan-tree-dump-times forwprop2 "memset" 0
Date: Mon, 31 Mar 2014 18:33:00 -0000 [thread overview]
Message-ID: <bug-60707-4-uA624pxdYQ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60707-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60707
--- Comment #2 from dave.anglin at bell dot net ---
On 3/31/2014 4:27 AM, rguenth at gcc dot gnu.org wrote:
> Already xfailed for mips. You may want to check history to see if it's
> applicable to xfail on hppa as well.
I just noticed that this bug may have been recently fixed. Test
didn't fail on last hppa2.0w-hp-hpux11.11 build.
Need to check whether it is also fixed on linux.
Looking at history, I didn't get a clear answer as to whether xfail
should apply to hppa as well.
next prev parent reply other threads:[~2014-03-31 18:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-29 19:48 [Bug tree-optimization/60707] New: " danglin at gcc dot gnu.org
2014-03-31 8:27 ` [Bug tree-optimization/60707] " rguenth at gcc dot gnu.org
2014-03-31 18:33 ` dave.anglin at bell dot net [this message]
2014-08-07 21:45 ` danglin at gcc dot gnu.org
2014-08-07 21:47 ` danglin at gcc dot gnu.org
2014-08-07 21:49 ` danglin 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-60707-4-uA624pxdYQ@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).