From: Richard Earnshaw <rearnsha@gcc.gnu.org>
To: Joern Rennecke <joern.rennecke@superh.com>
Cc: Dave Korn <dk@artimi.com>, gcc@gcc.gnu.org
Subject: Re: Lousy scheduling decisions owing to bad interaction between sched and greg :(
Date: Fri, 03 Sep 2004 14:42:00 -0000 [thread overview]
Message-ID: <1094222545.1833.227.camel@pc960.cambridge.arm.com> (raw)
In-Reply-To: <200409031329.i83DTcJ23009@chloe.uk.w2k.superh.com>
On Fri, 2004-09-03 at 14:29, Joern Rennecke wrote:
> > ===================================================================
> > 4) Does an expander sound like the right solution to the problem?
> > ===================================================================
>
> Yes. You'll also have to have an insn predicate for movsi that rejects
> memory-memory moves to prevent the rtl optimizers from generating them.
It can't really be a predicate (in the strict sense) because they can
only validate one operand. Instead you need a final condition on the
insn that rejects it in the case where both operands turn out to be
memory operands. The ARM does this for its mov<mm> patterns as, I
suspect, do several ports.
R.
next prev parent reply other threads:[~2004-09-03 14:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-03 12:52 Dave Korn
2004-09-03 13:26 ` Joern Rennecke
2004-09-03 14:42 ` Richard Earnshaw [this message]
2004-09-03 16:35 ` Jeffrey A Law
2004-09-03 17:26 ` Lousy scheduling decisions owing to bad interaction betweensched " Dave Korn
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=1094222545.1833.227.camel@pc960.cambridge.arm.com \
--to=rearnsha@gcc.gnu.org \
--cc=dk@artimi.com \
--cc=gcc@gcc.gnu.org \
--cc=joern.rennecke@superh.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).