[Clfs-support] Assembler error when making target 'all-target-libgcc' with the 'thumb' ARM mode

[Andrew Bradford]

On Fri, Apr 1, 2011 at 8:56 AM, Angel Ivan Castell Rovira
<al004140 at gmail.com> wrote:
> According to table 6.1 on section 6.3 (ABI variables) it seems that mode
> "thumb" must be setup with CLFS_ABI="atpcs". That was wrong on my
> environment. However, I tested again with that variable fixed, and the error
> when building the static gcc is exactly the same:
>
> /home/clfs/sources/gcc-static-build/./gcc/xgcc
> -B/home/clfs/sources/gcc-static-build/./gcc/
> -B/home/clfs/cross-tools/armv4-linux-uclibc/bin/
> -B/home/clfs/cross-tools/armv4-linux-uclibc/lib/ -isystem
> /home/clfs/cross-tools/armv4-linux-uclibc/include -isystem
> /home/clfs/cross-tools/armv4-linux-uclibc/sys-include    -g -O2 -O2  -g -O2
> -DIN_GCC -DCROSS_DIRECTORY_STRUCTURE  -W -Wall -Wwrite-strings -Wcast-qual
> -Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition  -isystem
> ./include  -fomit-frame-pointer -fPIC -Wno-missing-prototypes -g
> -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED -Dinhibit_libc  -I. -I. -I../.././gcc
> -I../../../gcc-4.5.2/libgcc -I../../../gcc-4.5.2/libgcc/.
> -I../../../gcc-4.5.2/libgcc/../gcc -I../../../gcc-4.5.2/libgcc/../include
> -DHAVE_CC_TLS  -o _clear_cache.o -MT _clear_cache.o -MD -MP -MF
> _clear_cache.dep -DL_clear_cache -c
> ../../../gcc-4.5.2/libgcc/../gcc/libgcc2.c \
>
> /tmp/ccF3T7aD.s: Assembler messages:
> /tmp/ccF3T7aD.s:29: Error: invalid swi expression
> /tmp/ccF3T7aD.s:29: Error: value of 10420226 too large for field of 2 bytes
> at 2
> make[1]: *** [_clear_cache.o] Error 1
> make[1]: Leaving directory
> `/home/clfs/sources/gcc-static-build/armv4-linux-uclibc/libgcc'
> make: *** [all-target-libgcc] Error 2
>
> $ env | grep CLFS
> CLFS_HOST=i486-cross-linux-gnu
> CLFS_TARGET=armv4-linux-uclibc
> CLFS_ARM_ARCH=armv4t
> CLFS_ARM_MODE=thumb
> CLFS=/home/clfs
> CLFS_ARCH=arm
> CLFS_ABI=atpcs
> CLFS_ENDIAN=little
> CLFS_FLOAT=soft

Based on these problems, should thumb mode be taken out of the book?

If it doesn't work and (it seems) there's little excitement about
determining the root cause, I don't think it should stay in the book.
If it gets removed, a trac ticket can be opened to add thumb mode back
in.

-Andrew