[U-Boot-Users] ppc arch specific memcpy issue?
Using uboot 1.1.6 compiled with a powerpc gcc 4.1.0 cross compiler on a mpc5200 board and booting from flash. If I disable architecture specific bcopy, memmove and memcpy via __HAVE_ARCH_BCOPY etc, I'm able to boot up properly, in this case into GHS Integrity. If I use the architecture specific asm versions of these functions I get "CheckSuccess" errors.
Has anyone seen something similar? It appears as if the elf load doesn't do the same thing with the ppc optimized code but I would have thought someone would have noticed this sooner since lib_ppc/ppcstring.S appears to have been modified for quite some time now.
Chris
So no one has seen any issues with ppc specific memcpy/memmove in 1.1.6?
Chris
On 2/12/07, Chris Morgan chmorgan@gmail.com wrote:
Using uboot 1.1.6 compiled with a powerpc gcc 4.1.0 cross compiler on a mpc5200 board and booting from flash. If I disable architecture specific bcopy, memmove and memcpy via __HAVE_ARCH_BCOPY etc, I'm able to boot up properly, in this case into GHS Integrity. If I use the architecture specific asm versions of these functions I get "CheckSuccess" errors.
Has anyone seen something similar? It appears as if the elf load doesn't do the same thing with the ppc optimized code but I would have thought someone would have noticed this sooner since lib_ppc/ppcstring.S appears to have been modified for quite some time now.
Chris
participants (1)
-
Chris Morgan