On Wed, 3 Oct 2007, chaisc97 wrote:
> > * When gcc inserts a call to memcpy(), everything works wonderfully.
> > * When gcc decides it wants to inline its ARM assembly-optimized
> > version of memcpy(), the result is as if I called memcpy() with a
> > source address aligned to an int (haven't played with unaligned dest
> yet):
> >
> > memcpy(dest, src & ~3, n);
> >
> > It's as if I started the copy from an aligned address and therefore I
> > get unwanted garbage on dest before the actual data I need. Replacing
> > the call with my own copying in pure C just works, and so does the
> > real memcpy().
> i have the same problem, when i try to copy some data from
> mem(0x20200000), some time i get the correct value some times i get
> the wrong one, does anyone has any idea?
given that 0x20200000 is word aligned, I seriously doubt this is the same
problem. If you show your code people may be able to help you.
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/ts-7000/
<*> Your email settings:
Individual Email | Traditional
<*> To change settings online go to:
http://groups.yahoo.com/group/ts-7000/join
(Yahoo! ID required)
<*> To change settings via email:
<*> To unsubscribe from this group, send an email to:
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
|