Re: [PATCH, ARM] PR target/68059 libgcc should not use __write for printing fatal error

2015-11-05 Thread Szabolcs Nagy
On 05/11/15 15:59, Richard Earnshaw wrote: On 05/11/15 12:30, Szabolcs Nagy wrote: libgcc/config/arm/linux-atomic-64bit.c uses __write to print an error message if the 64bit xchg method is not available in the kernel. __write is not part of the public libc abi. Since this code is only run on l

Re: [PATCH, ARM] PR target/68059 libgcc should not use __write for printing fatal error

2015-11-05 Thread Richard Earnshaw
On 05/11/15 12:30, Szabolcs Nagy wrote: > libgcc/config/arm/linux-atomic-64bit.c uses __write to print an error > message if the 64bit xchg method is not available in the kernel. > > __write is not part of the public libc abi. Since this code is only > run on linux the write syscall can be invoke

[PATCH, ARM] PR target/68059 libgcc should not use __write for printing fatal error

2015-11-05 Thread Szabolcs Nagy
libgcc/config/arm/linux-atomic-64bit.c uses __write to print an error message if the 64bit xchg method is not available in the kernel. __write is not part of the public libc abi. Since this code is only run on linux the write syscall can be invoked directly. And __builtin_trap is a simpler way