public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bernds at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/44470] [4.6 Regression] Failed to bootstrap with - -with-arch=atom
Date: Mon, 16 Aug 2010 23:50:00 -0000	[thread overview]
Message-ID: <20100816234957.3442.qmail@sourceware.org> (raw)
In-Reply-To: <bug-44470-682@http.gcc.gnu.org/bugzilla/>



------- Comment #18 from bernds at gcc dot gnu dot org  2010-08-16 23:49 -------
I'm seeing some strange situations where this code is unnecessarily producing
lea insns even when not tuning for Atom.

This code looks very strange.  I don't understand why we aren't splitting to a
lea pattern anymore if we want to produce a lea insn.

Also, isn't the test for TARGET_OPT_AGU reversed?


-- 

bernds at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|FIXED                       |


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


  parent reply	other threads:[~2010-08-16 23:50 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-08 21:30 [Bug bootstrap/44470] New: " hjl dot tools at gmail dot com
2010-06-08 22:00 ` [Bug bootstrap/44470] " hjl dot tools at gmail dot com
2010-06-09  0:53 ` hjl dot tools at gmail dot com
2010-06-09  1:00 ` hjl dot tools at gmail dot com
2010-06-09  6:27 ` ubizjak at gmail dot com
2010-06-09  7:46 ` ubizjak at gmail dot com
2010-06-09  9:32 ` rguenth at gcc dot gnu dot org
2010-06-09 12:15 ` ubizjak at gmail dot com
2010-06-09 14:13 ` hjl dot tools at gmail dot com
2010-06-09 14:17 ` hjl dot tools at gmail dot com
2010-06-09 20:30 ` hjl dot tools at gmail dot com
2010-06-09 20:31 ` hjl dot tools at gmail dot com
2010-06-10  6:18 ` ubizjak at gmail dot com
2010-06-10 14:30 ` hjl dot tools at gmail dot com
2010-06-10 14:57 ` ubizjak at gmail dot com
2010-06-10 15:00 ` ubizjak at gmail dot com
2010-06-10 15:13 ` ubizjak at gmail dot com
2010-06-10 15:44 ` hjl dot tools at gmail dot com
2010-06-10 16:01 ` hjl at gcc dot gnu dot org
2010-06-10 19:16 ` hjl dot tools at gmail dot com
2010-08-16 23:50 ` bernds at gcc dot gnu dot org [this message]
2010-08-16 23:51 ` bernds at gcc dot gnu dot org
2010-08-17  0:10 ` hjl dot tools at gmail dot com
2010-08-17  0:11 ` hjl dot tools at gmail dot com
2010-08-17  0:17 ` bernds at gcc dot gnu dot org
2010-08-17  3:46 ` hjl dot tools at gmail dot com
2010-08-17  9:48 ` bernds at gcc dot gnu dot org
2010-08-17 14:48 ` hjl dot tools at gmail dot com
2010-08-18 20:13 ` ubizjak at gmail 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=20100816234957.3442.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).