public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/39976] [4.5/4.6/4.7 Regression] Big sixtrack degradation on powerpc 32/64 after revision r146817
Date: Sat, 05 Nov 2011 12:39:00 -0000	[thread overview]
Message-ID: <bug-39976-4-OoS5j0jyVr@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-39976-4@http.gcc.gnu.org/bugzilla/>

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

Richard Guenther <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |WAITING

--- Comment #35 from Richard Guenther <rguenth at gcc dot gnu.org> 2011-11-05 12:37:17 UTC ---
Asking for re-confirmation again.


  parent reply	other threads:[~2011-11-05 12:39 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-39976-4@http.gcc.gnu.org/bugzilla/>
2010-12-15 15:33 ` [Bug middle-end/39976] [4.5/4.6 " jakub at gcc dot gnu.org
2010-12-15 21:15 ` pthaugen at gcc dot gnu.org
2010-12-15 21:24 ` pthaugen at gcc dot gnu.org
2010-12-16 13:16 ` rguenth at gcc dot gnu.org
2011-04-28 15:34 ` [Bug middle-end/39976] [4.5/4.6/4.7 " rguenth at gcc dot gnu.org
2011-11-05 12:39 ` rguenth at gcc dot gnu.org [this message]
2011-11-09  0:13 ` pthaugen at gcc dot gnu.org
2011-11-17 15:22 ` wschmidt at gcc dot gnu.org
2011-11-17 15:49 ` wschmidt at gcc dot gnu.org
2011-11-17 17:12 ` matz at gcc dot gnu.org
2011-11-18 23:26 ` wschmidt at gcc dot gnu.org
2011-12-01 22:31 ` pinskia at gcc dot gnu.org
2011-12-08 22:03 ` wschmidt at gcc dot gnu.org
2011-12-08 22:16 ` wschmidt at gcc dot gnu.org
2011-12-09  9:05 ` rguenth at gcc dot gnu.org
2012-02-24  8:39 ` jiangning.liu at arm dot com

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-39976-4-OoS5j0jyVr@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).