From: Joern Rennecke <joern.rennecke@superh.com>
To: dk@artimi.com (Dave Korn)
Cc: gcc@gcc.gnu.org
Subject: Re: Lousy scheduling decisions owing to bad interaction between sched and greg :(
Date: Fri, 03 Sep 2004 13:26:00 -0000 [thread overview]
Message-ID: <200409031329.i83DTcJ23009@chloe.uk.w2k.superh.com> (raw)
In-Reply-To: <NUTMEGiSp5CiMSdqA0B00001137@NUTMEG.CAM.ARTIMI.COM> from "Dave Korn" at Sep 03, 2004 01:49:40
> ===================================================================
> 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.
next prev parent reply other threads:[~2004-09-03 13:26 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 [this message]
2004-09-03 14:42 ` Richard Earnshaw
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=200409031329.i83DTcJ23009@chloe.uk.w2k.superh.com \
--to=joern.rennecke@superh.com \
--cc=dk@artimi.com \
--cc=gcc@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).