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 target/55147] [4.8 Regression] x86: wrong code for 64-bit load
Date: Thu, 01 Nov 2012 09:27:00 -0000 [thread overview]
Message-ID: <bug-55147-4-PsnNbK7VFH@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55147-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55147
Uros Bizjak <ubizjak at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |4.8.0
Summary|x86: wrong code for 64-bit |[4.8 Regression] x86: wrong
|load |code for 64-bit load
--- Comment #4 from Uros Bizjak <ubizjak at gmail dot com> 2012-11-01 09:27:21 UTC ---
(In reply to comment #3)
> it creates the same number of insns/same quality (just slightly different RA
> decisions/scheduling) for f1-f3, but for f4 without bswapdi2 it creates
> slightly worse code (with bswapdi2 f4 needs just one call saved register,
> without it two, supposedly because both bswap insns are scheduled together.
We can live with that.
I have also checked that removing the pattern doesn't degrade TARGET_MOVBE, the
reason for their existence is PR53227.
Also, a regression from 4.7.
next prev parent reply other threads:[~2012-11-01 9:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-31 11:23 [Bug target/55147] New: " mans at mansr dot com
2012-10-31 15:39 ` [Bug target/55147] " jakub at gcc dot gnu.org
2012-10-31 15:48 ` ubizjak at gmail dot com
2012-10-31 16:07 ` jakub at gcc dot gnu.org
2012-11-01 9:27 ` ubizjak at gmail dot com [this message]
2012-11-01 9:44 ` [Bug target/55147] [4.8 Regression] " jakub at gcc dot gnu.org
2012-11-01 9:49 ` ubizjak at gmail dot com
2012-11-02 8:03 ` jakub at gcc dot gnu.org
2012-11-07 10:15 ` 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-55147-4-PsnNbK7VFH@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).