From: Richard Sandiford <richard.sandiford@linaro.org>
To: Richard Guenther <richard.guenther@gmail.com>
Cc: gcc-patches@gcc.gnu.org, zaks@il.ibm.com
Subject: Re: [4/4] Make SMS schedule register moves
Date: Tue, 30 Aug 2011 13:43:00 -0000 [thread overview]
Message-ID: <g41uw3cbn5.fsf@richards-thinkpad.stglab.manchester.uk.ibm.com> (raw)
In-Reply-To: <CAFiYyc3fDFDXy2UwQ9uM0A4ZykZ7B=v09J7S3wj2E5wKDLy4Fw@mail.gmail.com> (Richard Guenther's message of "Tue, 30 Aug 2011 14:33:22 +0200")
Richard Guenther <richard.guenther@gmail.com> writes:
> On Tue, Aug 30, 2011 at 2:29 PM, Richard Sandiford
> <richard.sandiford@linaro.org> wrote:
>> This is the move-scheduling patch itself. It should be fairly
>> self-explanatory. Let me know if it isn't, and I'll try to improve
>> the commentary.
>
> Can you add some testcases?
I don't think it's an easy thing to test for. E.g. with the resampling
loop in the covering message, there might well be a reasonable ii=27
schedule that doesn't need as many moves.
Richard
next prev parent reply other threads:[~2011-08-30 12:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-30 12:45 [0/4] " Richard Sandiford
2011-08-30 12:46 ` [1/4] SMS: remove register undo list Richard Sandiford
2011-08-30 13:04 ` [2/4] SMS: Use ids to represent ps_insns Richard Sandiford
2011-08-30 13:12 ` [3/4] SMS: Record moves in the partial schedule Richard Sandiford
2011-08-30 13:17 ` [4/4] Make SMS schedule register moves Richard Sandiford
2011-08-30 13:22 ` Richard Guenther
2011-08-30 13:43 ` Richard Sandiford [this message]
2011-08-30 13:50 ` Richard Guenther
2011-08-30 13:57 ` Richard Sandiford
[not found] <OFE173D50E.19DC6A3D-ONC2257912.007D3E72-C2257912.007D4640@il.ibm.com>
2011-09-22 17:38 ` Ayal Zaks
2011-09-22 22:33 ` Richard Sandiford
2011-09-23 7:49 ` Ayal Zaks
2011-09-28 16:16 ` Richard Sandiford
2011-10-10 1:10 ` Ayal Zaks
2011-10-10 12:17 ` Richard Sandiford
2011-10-10 15:52 ` Ayal Zaks
2011-10-11 8:49 ` Richard Sandiford
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=g41uw3cbn5.fsf@richards-thinkpad.stglab.manchester.uk.ibm.com \
--to=richard.sandiford@linaro.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=richard.guenther@gmail.com \
--cc=zaks@il.ibm.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).