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 tree-optimization/59501] [4.9 Regression] Vector Gather with GCC 4.9 2013-12-08 Snapshot
Date: Thu, 19 Dec 2013 18:09:00 -0000	[thread overview]
Message-ID: <bug-59501-4-feugwtDlkv@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59501-4@http.gcc.gnu.org/bugzilla/>

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|P3                          |P1
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2013-12-19
                 CC|                            |hjl at gcc dot gnu.org,
                   |                            |hubicka at gcc dot gnu.org,
                   |                            |jakub at gcc dot gnu.org
     Ever confirmed|0                           |1

--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
This regressed with r203171.  Before that change, -maccumulate-outgoing-args
was true, but now it isn't.  The changes I see in the RTL dumps is that there
is a (dead) load from r10 register into a pseudo from expand to jump pass, then
the RTL is pretty much the same (different insn numbers) until
pro_and_epilogue, which creates all the garbage.
The reason why the load from r10 is created and supposedly for the different
pro_and_epilogue behavior is ix86_get_drap_rtx:
  if (ix86_force_drap || !ACCUMULATE_OUTGOING_ARGS)
    crtl->need_drap = true;
But in the function in question, LRA has not spilled anything to the stack, the
stack actually isn't used at all, and neither is the drap reg live at the start
of the function (that would be another reason why we'd need to emit some
setting of the drap reg, but probably wouldn't need to dynamically realign the
stack).


  parent reply	other threads:[~2013-12-19 18:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-13 22:56 [Bug tree-optimization/59501] New: " freddie at witherden dot org
2013-12-19 13:31 ` [Bug tree-optimization/59501] [4.9 Regression] " rguenth at gcc dot gnu.org
2013-12-19 18:09 ` jakub at gcc dot gnu.org [this message]
2013-12-19 18:31 ` hjl.tools at gmail dot com
2013-12-19 18:39 ` jakub at gcc dot gnu.org
2013-12-19 18:43 ` hjl.tools at gmail dot com
2013-12-30  8:53 ` jakub at gcc dot gnu.org
2013-12-30  9:46 ` 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-59501-4-feugwtDlkv@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).