From: Mark Mitchell <mark@codesourcery.com>
To: amylaar@cygnus.co.uk
Cc: geoffk@cygnus.com, gcc@gcc.gnu.org
Subject: Re: ssa bootstrap problem on x86 (cmpstrsi_1 pattern)
Date: Thu, 27 Jul 2000 17:22:00 -0000 [thread overview]
Message-ID: <20000727172208M.mitchell@codesourcery.com> (raw)
In-Reply-To: <200007272359.AAA01850@phal.cygnus.co.uk>
>>>>> "Joern" == Joern Rennecke <amylaar@cygnus.co.uk> writes:
>> The only reason clobbers appear this early in the compiler is
>> that GCC generates machine-specific code very early. There is
>> no operation
Joern> That is not true. When gcc synthesizes a move that is
Joern> wider than the widest one available in the machine
Joern> description, it first clobbers the destination, then does a
Joern> series of moves into SUBREGs of the destination.
But, again, isn't that a machine-specific issue? These moves could be
represented directly as a SET and then resolved to an operation
involving SUBREGs and CLOBBERs later.
--
Mark Mitchell mark@codesourcery.com
CodeSourcery, LLC http://www.codesourcery.com
next prev parent reply other threads:[~2000-07-27 17:22 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-22 21:24 Geoff Keating
2000-07-23 0:50 ` Mark Mitchell
2000-07-24 11:51 ` Geoff Keating
2000-07-25 3:20 ` Richard Earnshaw
2000-07-26 22:55 ` Mark Mitchell
2000-07-27 12:50 ` Geoff Keating
2000-07-27 13:10 ` Mark Mitchell
2000-07-27 14:48 ` Richard Henderson
2000-07-27 15:13 ` Mark Mitchell
2000-07-27 15:14 ` Richard Henderson
2000-07-27 15:28 ` Mark Mitchell
2000-07-27 15:35 ` Richard Henderson
2000-07-27 15:42 ` Mark Mitchell
2000-07-27 15:46 ` Geoff Keating
2000-07-27 15:44 ` Geoff Keating
2000-07-27 16:01 ` Mark Mitchell
2000-07-27 16:59 ` Joern Rennecke
2000-07-27 17:22 ` Mark Mitchell [this message]
2000-07-27 17:57 ` Michael Meissner
2000-07-27 18:31 ` Mark Mitchell
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=20000727172208M.mitchell@codesourcery.com \
--to=mark@codesourcery.com \
--cc=amylaar@cygnus.co.uk \
--cc=gcc@gcc.gnu.org \
--cc=geoffk@cygnus.com \
/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).