Bart De VOS pointed out that removing absolute paths from the libc linker scripts is plainly wrong.
It dates from dawn ages of the original crosstool code, and is not well explained. At that time, binutils might not understand the sysroot stuff, and it was necessary to remove absolute paths in that case.
/trunk/scripts/build/libc/glibc.sh | 14 2 12 0 ++------------
1 file changed, 2 insertions(+), 12 deletions(-)
1 diff -durN gcc-3.4.6.orig/gcc/config/arm/arm.c gcc-3.4.6/gcc/config/arm/arm.c
2 --- gcc-3.4.6.orig/gcc/config/arm/arm.c 2007-08-15 22:57:51.000000000 +0200
3 +++ gcc-3.4.6/gcc/config/arm/arm.c 2007-08-15 22:57:51.000000000 +0200
6 adjacent_mem_locations (rtx a, rtx b)
8 + /* We don't guarantee to preserve the order of these memory refs. */
9 + if (volatile_refs_p (a) || volatile_refs_p (b))
12 if ((GET_CODE (XEXP (a, 0)) == REG
13 || (GET_CODE (XEXP (a, 0)) == PLUS
14 && GET_CODE (XEXP (XEXP (a, 0), 1)) == CONST_INT))
15 @@ -4611,6 +4615,17 @@
18 val_diff = val1 - val0;
22 + /* If the target has load delay slots, then there's no benefit
23 + to using an ldm instruction unless the offset is zero and
24 + we are optimizing for size. */
25 + return (optimize_size && (REGNO (reg0) == REGNO (reg1))
26 + && (val0 == 0 || val1 == 0 || val0 == 4 || val1 == 4)
27 + && (val_diff == 4 || val_diff == -4));
30 return ((REGNO (reg0) == REGNO (reg1))
31 && (val_diff == 4 || val_diff == -4));