Dear Stephen Warren,
In message 4F05FCBD.2040207@nvidia.com you wrote:
No, this is NOT a solution, it is a workaround for an inappropriate toolchain. If you want to build code for an armv4t system, you must use a tool chain that supports it.
But we don't want to generate code for ARMv4 in general, but rather
Then just turn on the ARMv4 specific options (-march=armv4t -mno-thumb -mthumb-interwork -mtune=arm920t ???) for the files that need it.
But as soon as any of these files liks code from libgcc you have to decide.
ARMv7 as the toolchain does. Only a tiny part of the code needs to be built for ARMv4, and in general we want to benefit from using ARMv7.
Then you should probably still link against a ARMv4 specific libgcc.
If you were building U-Boot's libgcc code with optimization set for ARMv7 this would not fix anything.
Best regards,
Wolfgang Denk