public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "amker at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/66612] [6 regression] FAIL: gcc.target/powerpc/20050830-1.c scan-assembler bdn
Date: Fri, 03 Jul 2015 02:00:00 -0000 [thread overview]
Message-ID: <bug-66612-4-2LrgZJA4B9@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-66612-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66612
amker at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2015-07-03
Ever confirmed|0 |1
--- Comment #6 from amker at gcc dot gnu.org ---
This relates to cost computation on powerpc64.
next prev parent reply other threads:[~2015-07-03 2:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-20 11:11 [Bug tree-optimization/66612] New: [6 regrssion] " schwab@linux-m68k.org
2015-06-20 11:14 ` [Bug tree-optimization/66612] [6 regression] " schwab@linux-m68k.org
2015-06-23 2:33 ` amker at gcc dot gnu.org
2015-07-02 9:22 ` amker at gcc dot gnu.org
2015-07-02 9:47 ` schwab@linux-m68k.org
2015-07-02 11:00 ` amker at gcc dot gnu.org
2015-07-03 2:00 ` amker at gcc dot gnu.org [this message]
2015-07-03 3:06 ` amker 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-66612-4-2LrgZJA4B9@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).