From: Geoff Keating <geoffk@cygnus.com>
To: Jan Hubicka <jh@suse.cz>
Cc: gcc@gcc.gnu.org
Subject: Re: SUBREGs and modes
Date: Wed, 02 Aug 2000 12:40:00 -0000 [thread overview]
Message-ID: <jm66pj78q0.fsf@envy.cygnus.com> (raw)
In-Reply-To: <20000802182923.B20604@atrey.karlin.mff.cuni.cz>
Jan Hubicka <jh@suse.cz> writes:
> Don't know - perhaps it would be better to wait for the SUBREG_BYTE
> patches. The prbolem I am having is that we prohibit SUBREGs of
> const_int s lurking around the RTL stream and currently gcse is
> creating them, since it fails to simplify the SUBREGs of constants
> substitued to registers with NON-SImode and WORDNUM nonzero. This
> also disables any const propagation on these beast too - in the CSE,
> gcse and combine :(
Actually, we don't. It used to be that when cross-compiling you could
get constructs like:
(subreg:SF (const_int 0x40800000) 0)
but a patch I committed about two weeks ago causes this case to only
happen when the FP emulator is not in use, which at present only
happens on VMS.
Now, I wouldn't _recommend_ such things. As you've noticed, it hurts
optimisation. gen_lowpart_common is the routine that knows how to fix
them.
Also, the reason for the patch is that PREFERRED_RELOAD_CLASS doesn't
work properly in the presence of such subregs, and it was easier to
ban them than to fix it.
--
- Geoffrey Keating <geoffk@cygnus.com>
prev parent reply other threads:[~2000-08-02 12:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-02 5:49 Jan Hubicka
2000-08-02 5:58 ` Jakub Jelinek
2000-08-02 8:39 ` Joern Rennecke
2000-08-02 8:49 ` Jan Hubicka
2000-08-02 9:13 ` Joern Rennecke
2000-08-02 9:30 ` Jan Hubicka
2000-08-02 12:40 ` Geoff Keating [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=jm66pj78q0.fsf@envy.cygnus.com \
--to=geoffk@cygnus.com \
--cc=gcc@gcc.gnu.org \
--cc=jh@suse.cz \
/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).