This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.

See the CrossGCC FAQ for lots more information.

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: ARM compiler misbehaves ?

From: Grant Edwards <grante at visi dot com>
To: "Dickinson, Derek" <Derek dot Dickinson at icn dot siemens dot com>
Cc: "'Richard Earnshaw'" <Richard dot Earnshaw at arm dot com>, Bill Gatliff <bgat at billgatliff dot com>, Svein-Erik Skjelbred <ixdp425 at skjelbred dot com>, crossgcc at sources dot redhat dot com
Date: Thu, 29 Apr 2004 10:03:41 -0500
Subject: Re: ARM compiler misbehaves ?
References: <EA78B62757AF1E4799828249310AC4CA05D17AD8@stca206a.bus.sc.rolm.com>

On Thu, Apr 29, 2004 at 07:46:50AM -0700, Dickinson, Derek wrote:
> >> Last time I checked (with the ARM and H8 gcc's) you could. It's
> >> just that dereferencing the pointer won't work right. Copying
> >> to/from the value of the pointer with memcpy() works fine.
> >> 
> >
> >No, even that isn't guaranteed, since the compiler is entitled to "know"
> >the implementation of memcpy, and therefore to implement it inline.
> 
> Is this true?  I thought memcpy was guaranteed to work on unaligned 
> addresses regardless of whether it is inline.

memcpy() has always worked for me with any alignment of source
and destination.

-- 
Grant Edwards
grante@visi.com

------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com

Follow-Ups:
- Re: ARM compiler misbehaves ?
  - From: Richard Earnshaw

References:
- RE: ARM compiler misbehaves ?
  - From: Dickinson, Derek

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