From: Alan Lehotsky <apl@alum.mit.edu>
To: Peter Barada <pbarada@mail.wm.sps.mot.com>
Cc: gcc@gcc.gnu.org, Peter.Barada@motorola.com
Subject: Re: Restricted addressing modes in ColdFire FPU for DFmode
Date: Fri, 07 Dec 2001 11:27:00 -0000 [thread overview]
Message-ID: <p04330109b836b7dcc7e0@[192.168.1.254]> (raw)
In-Reply-To: <200112071802.fB7I2cd25266@hyper.wm.sps.mot.com>
At 1:02 PM -0500 12/7/01, Peter Barada wrote:
>I'm working on adding the V4E ColdFire FPU instructions to gcc-2.95.3,
>and I've been having a very hard time convincing gcc to deal with the
>restricted addressing modes that the ColdFire FPU supports.
>
>.....
>(define_insn "movdf_v4e"
> [(set (match_operand:DF 0 "general_operand" "=f,<Q>S")
> (match_operand:DF 1 "general_operand" "f<Q>S,f"))]
> "TARGET_FPU_V4E"
> "*
>{
> return \"fmove%.d %1,%0\";
>}")
>
What happens if you change the predicate in the define_insn to
"nonimmedate_operand"
for BOTH operands[0] and operands[1]?
That would cause the combined instruction to fail being recognized...
--
------------------------------------------------------------------------
Quality Software Management
http://home.earthlink.net/~qsmgmt
apl@alum.mit.edu
(978)287-0435 Voice
(978)808-6836 Cell
(978)287-0436 Fax
Software Process Improvement and Management Consulting
Language Design and Compiler Implementation
next prev parent reply other threads:[~2001-12-07 18:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-07 10:13 Peter Barada
2001-12-07 11:27 ` Alan Lehotsky [this message]
2001-12-07 13:01 ` Peter Barada
2001-12-07 17:35 Re^2: " Peter Barada
2001-12-08 22:46 ` Richard Henderson
2001-12-10 8:15 ` Peter Barada
2001-12-10 13:11 ` Richard Henderson
2001-12-10 13:59 ` Peter Barada
2001-12-10 15:06 ` Peter Barada
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='p04330109b836b7dcc7e0@[192.168.1.254]' \
--to=apl@alum.mit.edu \
--cc=Peter.Barada@motorola.com \
--cc=gcc@gcc.gnu.org \
--cc=pbarada@mail.wm.sps.mot.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).