Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] package/uclibc: Enable compile in thumb mode configuration option
Date: Wed, 16 Dec 2015 23:08:16 +0100	[thread overview]
Message-ID: <5671E0D0.3030002@mind.be> (raw)
In-Reply-To: <20151215230351.5dc6e91d@free-electrons.com>

On 15-12-15 23:03, Thomas Petazzoni wrote:
> Paul,
> 
> On Sun, 13 Dec 2015 19:28:40 -0600, Paul Enman wrote:
[snip]
>> +ifeq ($(BR2_ARM_INSTRUCTIONS_THUMB2),y)
>> +define UCLIBC_ARM_THUMB_CONFIG
>> +	$(call KCONFIG_ENABLE_OPT,COMPILE_IN_THUMB_MODE,$(@D)/.config)
> 
> According to the help text of this uClibc option:
> 
>           Say 'y' here to force building uClibc in thumb mode.
>           Say 'n' to use your compiler's default mode.
> 
> When you have BR2_ARM_INSTRUCTIONS_THUMB2, the compiler already
> produces Thumb2 code by default, because the compiler is built with
> --with-mode=thumb.

 And in fact, the only thing that this option does is add -mthumb to CFLAGS,
which is indeed quite useless for our internal compiler.

 Or actually, it's not, because it also selects USE_BX and USE_LDREXSTREX.
USE_BX is currently handled by BR2_UCLIBC_ARM_BX but this is a cleaner way I
think. USE_LDREXSTREX is a better alternative to the SWP instruction so that's
interesting as well.

 Hm, looking at the uClibc code, there's something I don't quite understand.
USE_LDREXSTREX is selected by COMPILE_IN_THUMB_MODE, but in fact ldrex/strex are
only available on ARMv6+, so won't this break down on ARMv5?


 Regards,
 Arnout


> 
> So could you be more specific on which cases this patch is fixing by
> expanding the commit log?

[snip]



-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF

  parent reply	other threads:[~2015-12-16 22:08 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-04 22:56 [Buildroot] [PATCH 1/1] [1/1] package/uclibc: Enable compile in thumb mode when selected penman
2015-12-05 15:08 ` Arnout Vandecappelle
2015-12-08 19:34   ` Paul Enman
2015-12-14  1:28 ` [Buildroot] [PATCH v2] package/uclibc: Enable compile in thumb mode configuration option Paul Enman
2015-12-15 22:03   ` Thomas Petazzoni
2015-12-16  7:10     ` Waldemar Brodkorb
2015-12-16 21:49       ` Arnout Vandecappelle
2015-12-19  9:13         ` Waldemar Brodkorb
2015-12-31 19:44           ` Paul Enman
2015-12-16 22:08     ` Arnout Vandecappelle [this message]
2015-12-18  0:11       ` Paul Enman
2015-12-18 21:55         ` Arnout Vandecappelle
2015-12-19  9:35           ` Waldemar Brodkorb
2015-12-19  9:31         ` Waldemar Brodkorb
2015-12-23 16:16     ` Paul Enman

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=5671E0D0.3030002@mind.be \
    --to=arnout@mind.be \
    --cc=buildroot@busybox.net \
    /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