Re: is ARMv4T deprecated?
Bernhard Reutner-Fischer <[email protected]>
| Newsgroups | gmane.comp.lib.uclibc.general |
|---|---|
| Message-ID | <[email protected]> |
On April 15, 2015 9:47:31 PM GMT+02:00, Gustavo Zacarias <[email protected]> wrote: >On 04/15/2015 07:37 AM, Bernhard Reutner-Fischer wrote: > >> I cannot reproduce this. >> The arm920t eabi image seems to boot fine with qemu for a -cpu >arm926. >> >> Please send me your >> grep "memcpy\.o[sS]* " log.do_compile >> The file should be somewhere around your >> >tmp-uclibc/work/armv4t-oe-linux-uclibceabi/uclibc/0.9.33+gitAUTOINC+*/temp/log.do_compile > >I've managed to reproduce this in buildroot with the latest uclibc >snapshot. > >It seems to be toolchain-related, the table goes: >gcc 4.9.2 + binutils 2.25 + uclibc 0.9.33.2 = good >gcc 4.9.2 + binutils 2.25 + uclibc snapshot = bad >gcc 4.7.4 + binutils 2.22 + both uclibc versions = good > >I'll try to get more details, but i suspect gcc is at fault here. >Sergiy: which gcc version are you using? >(BTW, in BR we build uclibc in ARM mode, EABI mandates interworking and >trying to build it in THUMB mode fails because of register exhaustion, >haven't tried with snapshot). These spill failures should be fixed on master, fyi.