From: Richard Sandiford <richard@codesourcery.com>
To: Nick Clifton <nickc@redhat.com>
Cc: echristo@apple.com, gcc-patches@gcc.gnu.org
Subject: Re: RFA/RFC: GCC has an incorrect length for the ldc1 instruction
Date: Fri, 10 Aug 2007 07:58:00 -0000 [thread overview]
Message-ID: <87vebnddn2.fsf@firetop.home> (raw)
In-Reply-To: <46BC103B.4090007@redhat.com> (Nick Clifton's message of "Fri\, 10 Aug 2007 08\:14\:03 +0100")
Nick Clifton <nickc@redhat.com> writes:
> Hi Richard,
>> gcc/
>> * config/mips/mips-protos.h (mips_address_insns): Add a boolean
>> argument.
>> (mips_fetch_insns): Delete in favor of...
>> (mips_load_store_insns): ...this new function.
>> * config/mips/mips.c (mips_address_insns): Add a boolean argument
>> to say whether multiword moves _might_ be split.
>> (mips_fetch_insns): Delete in favor of...
>> (mips_load_store_insns): ...this new function.
>> (mips_rtx_costs): Update the call to mips_address_insns.
>> (mips_address_cost): Likewise.
>> * config/mips/mips.md (length): Use mips_load_store_insns instead
>> of mips_fetch_insns.
>> * config/mips/constraints.md (R): Use mips_address_insns rather
>> than mips_fetch_insns. Assume that the move never needs to be split.
>
> Are you going to apply this version of the patch, or may I do it on
> your behalf ?
Sorry for the delay. I've been really busy recently, and only started
running tests for the patch yesterday. I'll commit it today or tomorrow
if the results are OK.
Richard
next prev parent reply other threads:[~2007-08-10 7:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-07 8:07 Nick Clifton
2007-08-07 9:54 ` Richard Sandiford
2007-08-07 15:03 ` Nick Clifton
2007-08-10 7:15 ` Nick Clifton
2007-08-10 7:58 ` Richard Sandiford [this message]
2007-08-10 15:41 ` 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=87vebnddn2.fsf@firetop.home \
--to=richard@codesourcery.com \
--cc=echristo@apple.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=nickc@redhat.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).