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: Mon, 21 May 2018 10:15:35 -0700	[thread overview]
Message-ID: <CAJ86T=WijtRjvKttrfRHdL1H+u_oEqvMS4rz4oyBy4KBB3qpHw@mail.gmail.com> (raw)
In-Reply-To: <20180519074149.GB1395@jama>

On Sat, May 19, 2018 at 12:41 AM, Martin Jansa <martin.jansa@gmail.com> wrote:
> On Sat, May 19, 2018 at 12:31:51AM -0700, Andre McCurdy wrote:
>> 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?
>
> It's still more evidence then what you've shown that it should be in
> machine config.

I had two criteria for this change:

  1) Only change the default for cores which support Thumb2.

  2) Don't have any effect on distros or recipes which already define
their own policy for setting ARM_INSTRUCTION_SET (ie don't use
over-rides).

Setting a weak default from armv7a.inc seems to be the simplest and
cleanest way to meet those two criteria.


  reply	other threads:[~2018-05-21 17:15 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
2018-05-19  7:41           ` Martin Jansa
2018-05-21 17:15             ` Andre McCurdy [this message]
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=WijtRjvKttrfRHdL1H+u_oEqvMS4rz4oyBy4KBB3qpHw@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.