public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/55247] [4.8 Regression] internal compiler error: Max. number of generated reload insns per insn is achieved (90)
Date: Sat, 10 Nov 2012 09:22:00 -0000	[thread overview]
Message-ID: <bug-55247-4-emZNUp6X8g@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55247-4@http.gcc.gnu.org/bugzilla/>


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

--- Comment #8 from Uros Bizjak <ubizjak at gmail dot com> 2012-11-10 09:22:03 UTC ---
(In reply to comment #3)
> There are 2 issues here:
> 
> 1. Should we use
> 
>     movdqu    (%eax), %xmm0    # 19    *movti_internal_rex64/4    [length = 5]
>     movdqa    %xmm0, (%rsp)    # 29    *movti_internal_rex64/5    [length = 5]
>
> to copy 16 bytes?

Yes, and this is the intention of all these "!" marks.

> 2. Should we split *movti_internal_rex64 if -mno-sse is used?

Movti is used for TARGET_64BIT only. Please keep in mind that *_doubleword
instructions operate on TImode values, so we rely completely on register
allocator to NOT allocate XMM register moves in this case. According to the
documentation, "!" means that alternative is OK if no reloading is needed, so
this fits our purpose to use SSE moves unless we move value directly to TImode
arithmetic operation (*_doubleword patterns).


  parent reply	other threads:[~2012-11-10  9:22 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-09  2:34 [Bug rtl-optimization/55247] New: " hjl.tools at gmail dot com
2012-11-09  2:34 ` [Bug rtl-optimization/55247] " hjl.tools at gmail dot com
2012-11-09  5:09 ` hjl.tools at gmail dot com
2012-11-09 19:42 ` vmakarov at redhat dot com
2012-11-10  1:32 ` hjl.tools at gmail dot com
2012-11-10  1:39 ` hjl.tools at gmail dot com
2012-11-10  1:58 ` hjl.tools at gmail dot com
2012-11-10  2:30 ` hjl.tools at gmail dot com
2012-11-10  9:15 ` ubizjak at gmail dot com
2012-11-10  9:22 ` ubizjak at gmail dot com [this message]
2012-11-10 11:28 ` uros at gcc dot gnu.org
2012-11-10 11:47 ` [Bug middle-end/55247] " ubizjak at gmail dot com
2012-11-10 11:56 ` ubizjak at gmail dot com
2012-11-10 19:02 ` [Bug rtl-optimization/55247] " hjl.tools at gmail dot com
2012-11-10 19:11 ` hjl.tools at gmail dot com
2012-11-10 19:41 ` ubizjak at gmail dot com
2012-11-11 21:53 ` ebotcazou at gcc dot gnu.org
2012-11-11 23:55 ` hjl.tools 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=bug-55247-4-emZNUp6X8g@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).