Re: [PATCH] Update compilation flags with core specific options

2013-07-24 Thread Scott Wood
On 07/24/2013 11:25:52 AM, Udma Catalin-Dan-B32721 wrote: > This breaks the vdso for e500v1/v2 (userspace dies with SIGILL), since > KBUILD_CFLAGS doesn't get used when building asm files, and the vdso > uses mftbu/mftbl which are not being assembled to the form that > e500v1/v2 support. > > We

RE: [PATCH] Update compilation flags with core specific options

2013-07-24 Thread Udma Catalin-Dan-B32721
> This breaks the vdso for e500v1/v2 (userspace dies with SIGILL), since > KBUILD_CFLAGS doesn't get used when building asm files, and the vdso > uses mftbu/mftbl which are not being assembled to the form that > e500v1/v2 support. > > We should be setting -mcpu=whatever and -msoft-float in both CF

Re: [PATCH] Update compilation flags with core specific options

2013-07-23 Thread Scott Wood
On 07/02/2013 06:20:04 AM, Catalin Udma wrote: If CONFIG_E500 is enabled, the compilation flags are updated specifying the target core -mcpu=e5500/e500mc/8540 Also remove -Wa,-me500, being incompatible with -mcpu=e5500/e6500 The assembler option is redundant if the -mcpu= flag is set. The patch f

Re: [PATCH] Update compilation flags with core specific options

2013-07-09 Thread Scott Wood
On 07/02/2013 06:20:04 AM, Catalin Udma wrote: If CONFIG_E500 is enabled, the compilation flags are updated specifying the target core -mcpu=e5500/e500mc/8540 Also remove -Wa,-me500, being incompatible with -mcpu=e5500/e6500 The assembler option is redundant if the -mcpu= flag is set. The patch f