This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Question about movM insn restrictions

From: Richard Henderson <rth at redhat dot com>
To: Richard dot Earnshaw at arm dot com
Cc: DJ Delorie <dj at redhat dot com>, marekm at amelek dot gda dot pl, gcc at gcc dot gnu dot org
Date: Fri, 10 May 2002 13:50:16 -0700
Subject: Re: Question about movM insn restrictions
References: <200205101727.g4AHRIo30466@greed.delorie.com> <200205101741.SAA13120@cam-mail2.cambridge.arm.com>

On Fri, May 10, 2002 at 06:41:27PM +0100, Richard Earnshaw wrote:
> Even this isn't enough.  Reload relies on being able to generate a valid 
> move insn directly, using
> 
>      insn = emit_insn (gen_rtx_SET (VOIDmode, out, in));

No it doesn't.  It uses that if reload_inX and reload_outX
do not exist.


r~

References:
- Re: Question about movM insn restrictions
  - From: DJ Delorie
- Re: Question about movM insn restrictions
  - From: Richard Earnshaw

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]