public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/45670] [4.6 Regression] Less efficient x86 addressing mode selection on 4.6, causes -Os size regression from 4.5
Date: Fri, 05 Nov 2010 10:03:00 -0000	[thread overview]
Message-ID: <bug-45670-4-fZqtLgKoGy@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-45670-4@http.gcc.gnu.org/bugzilla/>

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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jakub at gcc dot gnu.org

--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> 2010-11-05 10:03:15 UTC ---
Well, it is actually very much related to that reversion.  While it didn't
regress in between 161907 and 162617, it regressed from the MEM_REF merge till
161906 and from 162618 onwards.
The problem is that due to the MEM load combiner isn't able to fix this up, so
if we don't get it right during expansion, we are out of luck.  Looking at it
now...


  parent reply	other threads:[~2010-11-05 10:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-45670-4@http.gcc.gnu.org/bugzilla/>
2010-09-29 18:19 ` rguenth at gcc dot gnu.org
2010-11-05 10:03 ` jakub at gcc dot gnu.org [this message]
2010-11-05 10:49 ` jakub at gcc dot gnu.org
2010-11-05 11:17 ` ebotcazou at gcc dot gnu.org
2010-11-05 19:01 ` jakub at gcc dot gnu.org
2010-11-05 19:11 ` jakub 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-45670-4-fZqtLgKoGy@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).