[U-Boot] [PATCH 1/2] tegra2: Always build with USE_PRIVATE_LIBGCC=yes.
Simon Glass
sjg at chromium.org
Thu Jan 5 21:42:09 CET 2012
Hi,
On Thu, Jan 5, 2012 at 12:17 PM, Wolfgang Denk <wd at denx.de> wrote:
> Dear Stephen Warren,
>
> In message <4F05FCBD.2040207 at 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.
Perhaps we could adjust Tegra's config.mk to use ARMv4T when not
building with the private libgcc?
>
>> 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.
>
It might be possible to specify ARMv4T on the link flags and have it
pick up the v4T library, even if nearly everything else is ARMv7?
Regards,
Simon
> Best regards,
>
> Wolfgang Denk
>
> --
> DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
> HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
> Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
> I'd rather be led to hell than managed to heaven.
More information about the U-Boot
mailing list