public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "steven at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/27016] ARM optimizer produces severely suboptimal code
Date: Sat, 02 Jan 2010 01:06:00 -0000	[thread overview]
Message-ID: <20100102010552.2992.qmail@sourceware.org> (raw)
In-Reply-To: <bug-27016-12470@http.gcc.gnu.org/bugzilla/>



------- Comment #6 from steven at gcc dot gnu dot org  2010-01-02 01:05 -------
Comment #3 and comment #5 still true with "GCC: (GNU) 4.5.0 20090808
(experimental) [trunk revision 150579]" -> reconfirmed.


-- 

steven at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Last reconfirmed|2009-06-30 11:35:26         |2010-01-02 01:05:52
               date|                            |


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


  parent reply	other threads:[~2010-01-02  1:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-04  8:12 [Bug c/27016] New: " Eric dot Doenges at betty-tv dot com
2006-04-04  8:16 ` [Bug middle-end/27016] " pinskia at gcc dot gnu dot org
2006-04-04  9:14 ` Eric dot Doenges at betty-tv dot com
2009-06-30 11:35 ` steven at gcc dot gnu dot org
2009-06-30 13:21 ` steven at gcc dot gnu dot org
2009-06-30 13:27 ` steven at gcc dot gnu dot org
2010-01-02  1:06 ` steven at gcc dot gnu dot org [this message]
2010-02-12 22:52 ` [Bug target/27016] [4.3/4.4/4.5 Regression] " steven at gcc dot gnu dot org
2010-02-16 10:27 ` rguenth at gcc dot gnu dot org
2010-02-17 17:09 ` mmitchel at gcc dot gnu dot org
2010-02-21 14:32 ` steven at gcc dot gnu dot org
2010-02-26  1:23 ` law at redhat 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=20100102010552.2992.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).