Hi Zhenqiang. I've had a look at the difference between testsuite results on our current softfp Natty builders and the new hard float Precise builders. The diff and notes is at: http://people.linaro.org/~michaelh/incoming/hard-float-builder-diff.txt

There's a lot of commonality:

/usr/bin/ld: cannot find {S,g}crt1.o: builder fault. I've fixed this.

sorry, unimplemented: Thumb-1 hard-float VFP ABI errors: tests where they set the architecture to ARMv5T and use our default Thumb mode. This causes the compiler to fail as it doesn't support Thumb-1 with hard float.

arm_iwmmxt_ok5222.c:1:0: sorry, unimplemented: iWMMXt and hardware floating point

Some are real:

+FAIL: gcc.c-torture/compile/sync-3.c -O0 (test for excess errors) /tmp/cc3ufndj.s:436: Error: co-processor offset out of range

+FAIL: gcc.dg/pr48335-2.c (test for excess errors) pr48335-2.c:19:30: internal compiler error: in expand_expr_addr_expr_1, at expr.c:7527

+FAIL: gcc.dg/pr48335-5.c (test for excess errors) pr48335-5.c:17:1: error: unrecognizable insn: (insn 11 10 12 3 (set (reg:DI 141) (unspec:DI [ (mem/c:DI (plus:SI (reg/f:SI 129 virtual-stack-vars) (const_int -8 [0xfffffffffffffff8])) [2 S8 A32]) ] UNSPEC_MISALIGNED_ACCESS)) /cbuild/slaves/ursa2/gcc-linaro-4.7+bzr114988~zhenqiang-chen~gnueabihf/gcc/gcc-linaro-4.7/gcc/testsuite/gcc.dg/pr48335-5.c:16 -1 (nil))

+FAIL: gcc.dg/torture/stackalign/builtin-apply-2.c -O0 execution test

Some are marked as unsupported but shouldn't be:

+UNSUPPORTED: gcc.dg/tree-ssa/gen-vect-11a.c +UNSUPPORTED: gcc.dg/tree-ssa/gen-vect-11b.c +UNSUPPORTED: gcc.dg/tree-ssa/gen-vect-11.c +UNSUPPORTED: gcc.dg/tree-ssa/gen-vect-11c.c +UNSUPPORTED: gcc.dg/tree-ssa/gen-vect-25.c +UNSUPPORTED: gcc.dg/tree-ssa/gen-vect-26.c +UNSUPPORTED: gcc.dg/tree-ssa/gen-vect-28.c +UNSUPPORTED: gcc.dg/tree-ssa/gen-vect-2.c +UNSUPPORTED: gcc.dg/tree-ssa/gen-vect-32.c

Could you look into the unsupported ones please? I'll fix the crt1 problems and respin the build.

-- Michael