All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andre McCurdy <armccurdy@gmail.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] arch-armv7a.inc: default to Thumb2 instruction set for armv7a and above
Date: Sat, 19 May 2018 00:31:51 -0700	[thread overview]
Message-ID: <CAJ86T=Ux8rM19VEdrG+cT1B08PmMQPB4TbeLj57P8zqfBw+cpw@mail.gmail.com> (raw)
In-Reply-To: <20180519071154.GA1395@jama>

On Sat, May 19, 2018 at 12:11 AM, Martin Jansa <martin.jansa@gmail.com> wrote:
> On Fri, May 18, 2018 at 11:48:45PM -0700, Andre McCurdy wrote:
>> On Fri, May 18, 2018 at 10:42 PM, Martin Jansa <martin.jansa@gmail.com> wrote:
>> > This variable was always meant to be used from DISTRO config
>>
>> I'm not sure if that's true. Do you have a reference?
>
> http://git.openembedded.org/openembedded-core/commit/?id=951200673af27538beaef647a33308b4f15d1fb0
> "in case we have MACHINE without "thumb" in TUNE_FEATURES and distro setting ARM_INSTRUCTION_SET to "thumb""
>
> https://github.com/Angstrom-distribution/meta-angstrom/blob/master/conf/distro/include/angstrom.inc#L39
> https://github.com/shr-distribution/meta-smartphone/blob/fido/meta-shr-distro/conf/distro/shr.conf#L150

Certainly there are distros which force ARM_INSTRUCTION_SET. I'm not
sure if that's evidence that machines shouldn't set a default though?

>> >, why not add it
>> > to:
>> > oe-core/meta/conf/distro/include/default-distrovars.inc
>> > or
>> > oe-core/meta/conf/distro/include/tcmode-default.inc
>> >
>> > ?
>>
>> Because then it would either apply to all ARM machines, including
>> those which only support Thumb1, which isn't ideal. Keeping it as part
>> of the machine config makes it easy to apply selectively to armv7a and
>> above where we know it's safe and desirable. Distros can of course
>> still over-ride (ie the machine only sets a weak default).
>
> You can still enable it with weak assignment only for some architectures
> like Angstrom does. But I don't see any reason why not enable it for all
> architectures? Yes Thumb1 isn't as good as Thumb2 but still many people
> are using it

I'm not sure if there are "many people" still trying to persevere with
Thumb1. Maybe there are a few masochists left, but I guess they
probably have their own distros and don't rely on the oe-core
defaults.

My approach is to try to make small, safe, incremental improvements
and doing anything which might change the default instruction set to
Thumb for CPUs which can only support Thumb1 doesn't fit that
approach.

>, why shouldn't oe-core be tested with thumb enabled (with
> armv5te qemuarm?), see:
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=9213
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=7717
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=1709
>
>> Is there a specific problem you see with the current patch?
>
> DISTROs doing multi machine builds already need to select the right
> DEFAULTTUNEs to find good compromise with common denominator of the
> MACHINEs they want to support (or groups of MACHINEs they want to
> support). Supporting or not supporting thumb at all is part of that
> question so DISTRO should decide that, tune files already have the thumb
> knob in TUNE_FEATURES to say which MACHINE is capable of supporting it.

Setting a weak default for armv7a and above from the machine config
doesn't change any of that. Distros still have full control.


  reply	other threads:[~2018-05-19  7:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-18 22:50 [PATCH] arch-armv7a.inc: default to Thumb2 instruction set for armv7a and above Andre McCurdy
2018-05-18 23:40 ` Khem Raj
2018-05-19  5:42   ` Martin Jansa
2018-05-19  6:48     ` Andre McCurdy
2018-05-19  7:11       ` Martin Jansa
2018-05-19  7:31         ` Andre McCurdy [this message]
2018-05-19  7:41           ` Martin Jansa
2018-05-21 17:15             ` Andre McCurdy
2018-05-22  9:58 Jef.Driesen
2018-05-22 10:33 ` Khem Raj
2018-06-04 21:33   ` Andre McCurdy
2018-06-26 19:52     ` Andre McCurdy

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='CAJ86T=Ux8rM19VEdrG+cT1B08PmMQPB4TbeLj57P8zqfBw+cpw@mail.gmail.com' \
    --to=armccurdy@gmail.com \
    --cc=martin.jansa@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.