is ARMv4T deprecated?

[Bernhard Reutner-Fischer]

On 15 April 2015 at 22:34, Sergiy Kibrik <sakib at meta.ua> wrote:
> On 4/15/15 1:37 PM, Bernhard Reutner-Fischer wrote:
>> On 9 April 2015 at 20:02, Sergiy Kibrik <sakib at meta.ua> wrote:
>>>
>>> On 4/8/15 10:04 AM, Bernhard Reutner-Fischer wrote:
>>>> On April 6, 2015 10:08:57 PM GMT+02:00, Bernhard Reutner-Fischer <rep.dot.nop at gmail.com> wrote:
>>>>> On April 5, 2015 9:30:30 PM GMT+02:00, Sergiy Kibrik <sakib at meta.ua>
>>>>> wrote:
>>>>>> hi All,
>>>>>> Recently I've been trying to use uClibc for quite old arm920t-based
>>>>>> board.
>>>>
>>>> Do you use  -mthumb-interwork ?
>>>
>>> yes, it's enabled by default in yocto
>>
>> I cannot reproduce this.
>> The arm920t eabi image seems to boot fine with qemu for a -cpu arm926.
>
> isn't arm926 based on ARMv5T?

Could be. Yes, it seems it is.
There's no V4 support in qemu it seems, at least ATM.
>
>> 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
>
> here it goes: http://pastebin.com/VGqf31ac

arm-poky-linux-uclibceabi-gcc -march=armv4t -marm -mthumb-interwork
-msoft-float -mlittle-endian -mthumb

I see no notion of a tune?

IIRC armv4t defaulted to arm7TDMI. Given that OE usually does not
configure for a default CPU (AFAICS) you have to pass a proper tune.

My 920t build used:
arm-oe-linux-uclibceabi-gcc -march=armv4t -mthumb  -mthumb-interwork
-O2 -mtune=arm920t

in your local.conf, try:
FULL_OPTIMIZATION = "-O2 -mtune=arm920t"
ARM_INSTRUCTION_SET := "thumb"

maybe you need some additional settings like DEFAULTTUNE TUNE_ARCH
TUNE_PKGARCH that you certainly use already.

HTH,