This is the mail archive of the gcc-patches@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: [m68k] Fix and improve ColdFire function prologue/epilogue generation

From: Bernardo Innocenti <bernie at develer dot com>
To: Andreas Schwab <schwab at suse dot de>
Cc: Richard Henderson <rth at redhat dot com>, gcc-patches at gcc dot gnu dot org, Peter Barada <peter at baradas dot org>
Date: Wed, 03 Sep 2003 15:48:26 +0200
Subject: Re: [m68k] Fix and improve ColdFire function prologue/epilogue generation
Organization: Develer S.r.l.
References: <200308130240.03115.bernie@develer.com> <20030828231409.GE5175@redhat.com> <3F55D07A.9010801@develer.com> <jer82y3vq2.fsf@sykes.suse.de>

Andreas Schwab wrote:

Bernardo Innocenti <bernie@develer.com> writes:

Hmmm does 'movem.l regs,(An)' work on m68k the same way it
does on ColdFire? That is, does it increment the
destination pointer after each write?


This is not a post-inc addressing mode, so the destination register
remains of course unchanged.  But the registers will surely be stored at
increasing memory addresses, if you mean that.

That's fine then - it's exactly the way ColdFire does it...


--
 // Bernardo Innocenti - Develer S.r.l., R&D dept.
\X/  http://www.develer.com/

Please don't send Word attachments - http://www.gnu.org/philosophy/no-word-attachments.html

References:
- Re: [m68k] Fix and improve ColdFire function prologue/epilogue generation
  - From: Bernardo Innocenti
- Re: [m68k] Fix and improve ColdFire function prologue/epiloguegeneration
  - From: Andreas Schwab

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