This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Restricted addressing modes in ColdFire FPU for DFmode
- From: Alan Lehotsky <apl at alum dot mit dot edu>
- To: Peter Barada <pbarada at mail dot wm dot sps dot mot dot com>
- Cc: gcc at gcc dot gnu dot org, Peter dot Barada at motorola dot com
- Date: Fri, 7 Dec 2001 13:22:34 -0500
- Subject: Re: Restricted addressing modes in ColdFire FPU for DFmode
- References: <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