From: Albert ARIBAUD <albert.aribaud@free.fr>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC PATCH 1/2] armv7: enable Thumb build for armv7
Date: Thu, 24 Mar 2011 15:45:51 +0100 [thread overview]
Message-ID: <4D8B591F.3010206@free.fr> (raw)
In-Reply-To: <4D81B882.30202@ti.com>
Le 17/03/2011 08:30, Aneesh V a ?crit :
> Albert,
>
> On Wednesday 16 March 2011 10:55 PM, Albert ARIBAUD wrote:
>> Le 16/03/2011 09:39, Aneesh V a ?crit :
> [snip ..]
>>
>> Some toolchains in current use (notably the one provided with ELDK 4.2,
>> and possibly others) do not support -march=armv7[-a]. Do we really need
>> armv7 instructions?
>
> 'cc-option' will make sure that build won't break for old compilers. We
> can do something like this:
>
> PLATFORM_CPPFLAGS += $(call cc-option,-march=armv7-a, -march=armv5)
>
> We are not planning to use armv7-a instructions in the code. In fact,
> recently I removed even an armv5 instruction from armv7 generic code in
> the interest of not breaking Tegra2.
>
> However, keeping -march=armv7-a (armv6 and above) helps in having
> Thumb2, which I believe is a good compromise between code density and
> performance.
>
> So, OMAP4 U-Boot when built with ELDK will give you Thumb1 code where
> as when it is built with newer compilers it will give you Thumb2 code.
> As long we don't use non-compliant assembly instructions, both should
> build and work fine.
>
> br,
> Aneesh
Understood. As for the question about config options (assuming I got it
right) I'd rather have the SoC define which -march it wants, and only
have a CONFIG for saying if we want thumb or not.
Amicalement,
--
Albert.
prev parent reply other threads:[~2011-03-24 14:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-14 13:27 [U-Boot] [RFC PATCH 1/2] armv7: enable Thumb build for armv7 Aneesh V
2011-03-14 13:27 ` [U-Boot] [RFC PATCH 2/2] OMAP4: enable Thumb2 support for OMAP4 Aneesh V
2011-03-14 16:11 ` [U-Boot] [RFC PATCH 1/2] armv7: enable Thumb build for armv7 Loïc Minier
2011-03-15 4:01 ` Aneesh V
2011-03-15 11:54 ` Loïc Minier
2011-03-16 8:39 ` Aneesh V
2011-03-16 17:25 ` Albert ARIBAUD
2011-03-17 7:30 ` Aneesh V
2011-03-24 14:45 ` Albert ARIBAUD [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D8B591F.3010206@free.fr \
--to=albert.aribaud@free.fr \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox