public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vmakarov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/55829] [4.8 Regression] ICE: in curr_insn_transform, at lra-constraints.c:3069 with -msse3
Date: Wed, 09 Jan 2013 18:16:00 -0000	[thread overview]
Message-ID: <bug-55829-4-2t9jWnWxWN@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55829-4@http.gcc.gnu.org/bugzilla/>


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

--- Comment #10 from Vladimir Makarov <vmakarov at gcc dot gnu.org> 2013-01-09 18:15:52 UTC ---
(In reply to comment #9)
> gcc now generates:
> 
>         movq    p1(%rip), %r12  # 56    *movdi_internal_rex64/2 [length = 7]
>         movq    %r12, (%rsp)    # 57    *movdi_internal_rex64/4 [length = 4]
>         movddup (%rsp), %xmm1   # 23    *vec_concatv2df/3       [length = 5]
> 
> is there a reason not to load directly from p1, to avoid extra moves:
> 
>         movddup p1(%rip), %xmm1

I checked reload pass, it has the same problem (and generates even worse code:
+1 insn and using nonzero displacement).  It is possible to fix it, but it will
be not easy.  In any case, I don't think it will fixed soon as I have more
important LRA PRs.

I'll put it on my TODO list.


      parent reply	other threads:[~2013-01-09 18:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-30 15:17 [Bug rtl-optimization/55829] New: " zsojka at seznam dot cz
2012-12-31 10:29 ` [Bug rtl-optimization/55829] " pinskia at gcc dot gnu.org
2013-01-04  3:39 ` pinskia at gcc dot gnu.org
2013-01-07 15:45 ` rguenth at gcc dot gnu.org
2013-01-08  9:58 ` jakub at gcc dot gnu.org
2013-01-08 10:03 ` jakub at gcc dot gnu.org
2013-01-08 16:10 ` vmakarov at redhat dot com
2013-01-08 16:28 ` ubizjak at gmail dot com
2013-01-09 16:33 ` ubizjak at gmail dot com
2013-01-09 17:12 ` ubizjak at gmail dot com
2013-01-09 17:50 ` jakub at gcc dot gnu.org
2013-01-09 17:52 ` ubizjak at gmail dot com
2013-01-09 18:16 ` vmakarov at gcc dot gnu.org [this message]

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-55829-4-2t9jWnWxWN@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).