public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/19398] secondary reloads don't consider "m" alternatives
Date: Tue, 18 Jan 2005 11:20:00 -0000 [thread overview]
Message-ID: <20050118112024.4114.qmail@sourceware.org> (raw)
In-Reply-To: <20050112133406.19398.uros@kss-loka.si>
------- Additional Comments From rth at gcc dot gnu dot org 2005-01-18 11:20 -------
This doesn't really have anything to do with sse. We have a value in "f" and
decide it should be in "x", and discount the "m" alternative. Could be fixed
by having reload look at "m" when considering secondary reloads.
It's sure to be mildly complicated by wanting to not keep the value in memory
if it could be inherited by multiple instructions, but it's definitely a win
for x86 code density to avoid explicit loads when the value is otherwise unused.
The only target solution I can think of is peepholes. But we could easily need
Quite A Lot of them in the x86 port, so I don't think this an ideal solution.
--
What |Removed |Added
----------------------------------------------------------------------------
Component|target |rtl-optimization
Keywords|ssemmx |
Summary|Non-optimal code with |secondary reloads don't
|cvttss2si |consider "m" alternatives
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19398
next prev parent reply other threads:[~2005-01-18 11:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-12 13:34 [Bug target/19398] New: Non-optimal code with cvttss2si uros at kss-loka dot si
2005-01-12 15:56 ` [Bug target/19398] " pinskia at gcc dot gnu dot org
2005-01-14 23:21 ` pinskia at gcc dot gnu dot org
2005-01-18 11:20 ` rth at gcc dot gnu dot org [this message]
2005-01-18 12:22 ` [Bug rtl-optimization/19398] secondary reloads don't consider "m" alternatives uros at kss-loka dot si
2005-03-15 10:10 ` giovannibajo at libero dot it
2005-03-15 11:44 ` bernds_cb1 at t-online dot de
2005-03-15 12:23 ` giovannibajo at libero dot it
2005-03-15 12:35 ` uros at kss-loka dot si
2005-08-01 18:46 ` dalej at gcc dot gnu dot org
2005-08-08 9:58 ` bonzini at gcc dot gnu dot org
2005-08-08 10:17 ` bonzini at gcc dot gnu dot org
[not found] <bug-19398-1649@http.gcc.gnu.org/bugzilla/>
2006-10-21 19:27 ` uros at gcc dot gnu dot org
[not found] <bug-19398-4@http.gcc.gnu.org/bugzilla/>
2012-10-27 8:14 ` ubizjak at gmail dot com
2012-11-13 18:34 ` ubizjak at gmail dot com
2012-11-20 18:03 ` uros at gcc dot gnu.org
2012-11-20 18:30 ` ubizjak 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=20050118112024.4114.qmail@sourceware.org \
--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).