Re: FPU error with arm-linux-gnueabihf-gcc 3.7.3

2012-12-12 Thread Richard Earnshaw 

On 11/12/12 19:39, Matthew Gretton-Dann wrote:

On 10 December 2012 14:53, Zhangfei Gao  wrote:

We met build error when using arm-linux-gnueabihf-gcc 3.7.3 for Huawei
s40v200 kernel, which is 3.0.8, log is below.

HAVE issue:
gcc-linaro-arm-linux-gnueabihf-4.7-2012.11-20121123_linux.tar.bz2
gcc-linaro-arm-linux-gnueabihf-4.7-2012.10-20121022_linux.tar.bz2
gcc-linaro-arm-linux-gnueabi-2012.03-20120326_linux.tar.bz2, with build flag
--with-float=softfp


NO issue:
arm-eabi-gcc 4.4.0, which comes from android package.

Any suggestion?

Thanks

make[1]: `include/generated/mach-types.h' is up to date.
   CALLscripts/checksyscalls.sh
   CHK include/generated/compile.h
   AS  arch/arm/mach-godbox/hi_pm_sleep.o
arch/arm/mach-godbox/hi_pm_sleep.S: Assembler messages:
arch/arm/mach-godbox/hi_pm_sleep.S:456: Error: selected processor does not
support requested special purpose register -- `mrs r10,FPEXC'
arch/arm/mach-godbox/hi_pm_sleep.S:456: Error: selected processor does not
support requested special purpose register -- `msr FPEXC,r2'
arch/arm/mach-godbox/hi_pm_sleep.S:456: Error: selected processor does not
support requested special purpose register -- `mrs r2,FPSCR'
arch/arm/mach-godbox/hi_pm_sleep.S:546: Error: selected processor does not
support requested special purpose register -- `msr FPEXC,r2'
arch/arm/mach-godbox/hi_pm_sleep.S:546: Error: selected processor does not
support requested special purpose register -- `msr FPSCR,r10'
arch/arm/mach-godbox/hi_pm_sleep.S:546: Error: selected processor does not
support requested special purpose register -- `msr FPEXC,r9'
make[1]: *** [arch/arm/mach-godbox/hi_pm_sleep.o] Error 1
make: *** [arch/arm/mach-godbox] Error 2
make: *** Waiting for unfinished jobs


Can you show me the complete command line for assembling
arch/arm/mach-godbox/hi_pm_sleep.S into
arch/arm/mach-godbox/hi_pm_sleep.o please?  And also the output of gcc
-v?

My guess is that you are building GCC yourself have specified
--with-float=softfp, but not specified the actual floating point
architecture with --with-fpu= on the GCC configure line.  See the
documentation for -mfpu= in the GCC manuals to see what values are
valid here (again guessing but you probably want --with-fpu=vfpv3 or
--with-fpu=neon - but I don't know what architecture you are actually
compiling for).



Hmm, building the kernel with floating-point enabled is probably a 
no-no!  The kernel has to preserve the user-space floating point context 
as it isn't saved on kernel entry.  IIRC, insns in the kernel that 
really must access the co-processors have to use generic instrucions 
(MCR/MRC/LDC/STC, etc).


However, you might get a more useful answer if you talked to the kernel 
folk.


R.


___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-toolchain

Re: [PATCH] Cortex Strings AArch64 implementations of memcpy, memset, strcmp

2012-12-12 Thread Michael Hope 
On 11 December 2012 06:43, Marcus Shawcroft  wrote:
> This patch adds aarch64 implementations of memcpy, memset and strcmp
> to cortex strings.

Now that you've added multi-architecture support, I've added a native,
cross aarch32, and cross aarch64 build to our auto builders.  An
example build complete email is here:
 https://lists.launchpad.net/linaro-toolchain-builds/msg05186.html

with full results here:
 
http://cbuild.validation.linaro.org/build/cortex-strings-1.0+bzr90/logs/x86_64-precise-cbuild438-oort3-cortexa9r1/

Matt, it was surprisingly easy to add this via the variants system.
You could cross builds of other self contained packages in the same
way.

-- Michael

___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-toolchain

Clearing out past branches

2012-12-12 Thread Michael Hope 
Hi Ramana.  You have the following branches remaining on Launchpad:

 * lp:~ramana/gcc-linaro/47-lower-subreg-experiments
 * lp:~ramana/gcc-linaro/47-improve-neon-intrinsics
 * lp:~ramana/gcc-linaro/47-nobble-promote-mode
 * lp:~ramana/gcc-linaro/47-smin-umin-idiom

Which are obsolete, which should be spun out into backlog blueprints,
and which should be taken over by someone?

-- Michael

___
linaro-toolchain mailing list
linaro-toolchain@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-toolchain