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/67609] [5/6 Regression] Generates wrong code for SSE2 _mm_load_pd
Date: Fri, 16 Oct 2015 12:50:00 -0000	[thread overview]
Message-ID: <bug-67609-4-XJ8VfnlCxN@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-67609-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67609

--- Comment #9 from Vladimir Makarov <vmakarov at gcc dot gnu.org> ---
(In reply to Vladimir Makarov from comment #8)
> 
> Why do LRA and reload remove subregs of hard registers? That is because some
> subsequent optimizations can handle them.
> 

Sorry, it should be *can not handle*.

Basically keeping subregisters crashes other passes on GCC bootstrap.


  parent reply	other threads:[~2015-10-16 12:50 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-17 11:37 [Bug regression/67609] New: [Regression] " bisqwit at iki dot fi
2015-09-17 12:51 ` [Bug target/67609] [5/6 Regression] " rguenth at gcc dot gnu.org
2015-09-17 13:13 ` ubizjak at gmail dot com
2015-09-17 13:48 ` rguenth at gcc dot gnu.org
2015-09-17 18:09 ` [Bug regression/67609] " bisqwit at iki dot fi
2015-09-17 19:03 ` [Bug rtl-optimization/67609] " ubizjak at gmail dot com
2015-10-16 12:44 ` vmakarov at gcc dot gnu.org
2015-10-16 12:50 ` vmakarov at gcc dot gnu.org [this message]
2015-10-20 16:26 ` vmakarov at gcc dot gnu.org
2015-10-20 16:32 ` vmakarov at gcc dot gnu.org
2015-10-20 19:12 ` ubizjak at gmail dot com
2015-10-21  7:52 ` ubizjak at gmail dot com
2015-10-21 16:30 ` vmakarov at gcc dot gnu.org
2015-10-21 17:34 ` ubizjak at gmail dot com
2015-10-21 18:16 ` law at redhat dot com
2015-10-21 18:42 ` vmakarov at gcc dot gnu.org
2015-10-22  8:23 ` rguenth at gcc dot gnu.org
2015-10-22 12:49 ` law at redhat dot com
2015-10-22 13:40 ` rguenth at gcc dot gnu.org
2015-10-22 19:34 ` law at redhat dot com
2015-10-22 21:55 ` rth at gcc dot gnu.org
2015-10-22 22:54 ` rth at gcc dot gnu.org
2015-10-23  1:58 ` vmakarov at gcc dot gnu.org
2015-10-23  5:02 ` vmakarov at gcc dot gnu.org
2015-10-23  8:30 ` rguenth at gcc dot gnu.org
2015-10-23 13:14 ` vmakarov at gcc dot gnu.org
2015-10-23 19:06 ` rth at gcc dot gnu.org
2015-10-26 19:18 ` rth at gcc dot gnu.org
2015-10-26 21:48 ` vmakarov at gcc dot gnu.org
2015-10-27 10:18 ` rguenth at gcc dot gnu.org
2015-10-27 20:00 ` rth at gcc dot gnu.org
2015-10-29 18:37 ` rth at gcc dot gnu.org
2015-10-29 18:45 ` [Bug rtl-optimization/67609] [5 " rth 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-67609-4-XJ8VfnlCxN@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).