From: Nick Clifton <nickc@redhat.com>
To: Nick Clifton <nickc@redhat.com>,
echristo@apple.com, gcc-patches@gcc.gnu.org,
richard@codesourcery.com
Subject: Re: RFA/RFC: GCC has an incorrect length for the ldc1 instruction
Date: Tue, 07 Aug 2007 15:03:00 -0000 [thread overview]
Message-ID: <46B88950.8080000@redhat.com> (raw)
In-Reply-To: <87hcnb8ybn.fsf@firetop.home>
Hi Richard,
> Unfortunately, this isn't quite right. DFmode moves still take
> 2 instructions when the target is a GPR. For MIPS I, they will
> also take 2 instructions when the target is an FPR.
Darn, I was afraid that there might be a case like that.
> I think instead that mips_fetch_insns should try to prove that
> the move does not need to be split, and tell mips_address_insns
> about it. Does the patch below work for you?
It does. I also tested the patch on the slightly older sources that make up
the toolchain that was sent to our customer (which compiles the test case with
only one ldc1 instruction between a mfhi and a mult instruction) and it fixes
that toolchain as well.
Cheers
Nick
next prev parent reply other threads:[~2007-08-07 15:03 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 [this message]
2007-08-10 7:15 ` Nick Clifton
2007-08-10 7:58 ` Richard Sandiford
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=46B88950.8080000@redhat.com \
--to=nickc@redhat.com \
--cc=echristo@apple.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=richard@codesourcery.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).