This is the mail archive of the newlib@sourceware.org mailing list for the newlib 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: [patch] Fix and reenable memcpy/memset for m68k

From: "Aaron J. Grier" <aaron at frye dot com>
To: newlib at sources dot redhat dot com
Date: Tue, 1 May 2007 11:09:53 -0700
Subject: Re: [patch] Fix and reenable memcpy/memset for m68k
References: <200704302015.l3UKFFMO005039@sparrowhawk.codesourcery.com> <463653E6.2090600@oarcorp.com> <25F61B8D-114E-4BAB-82EC-29E8F0C1C959@aps.anl.gov> <46373F76.7090900@codesourcery.com>

On Tue, May 01, 2007 at 09:24:06AM -0400, Kazu Hirata wrote:
> Honestly, I didn't know anything about CPU32+.  If the architecture is
> not common these days, I think the unrolled version of memcpy is OK.

I was told by Charlie Melear at Motorola that "There is exactly ZERO
difference between the CPU32 and the CPU32+ instruction set.  The
difference is with the external bus structure."

isn't the Fido a CPU32-derivative?  does it have loop mode?

-- 
  Aaron J. Grier  |   Frye Electronics, Tigard, OR   |  aaron@frye.com

References:
- [patch] Fix and reenable memcpy/memset for m68k
  - From: Kazu Hirata
- Re: [patch] Fix and reenable memcpy/memset for m68k
  - From: Joel Sherrill
- Re: [patch] Fix and reenable memcpy/memset for m68k
  - From: Eric Norum
- Re: [patch] Fix and reenable memcpy/memset for m68k
  - From: Kazu Hirata

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