From: Martin Jansa <martin.jansa@gmail.com>
To: Kristof Robot <krirobo@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/2] feature-arm-thumb.inc: Use thumb instruction by default if TUNE_FEATURES thumb
Date: Mon, 3 Feb 2014 20:06:27 +0100 [thread overview]
Message-ID: <20140203190627.GH3698@jama> (raw)
In-Reply-To: <CAFgGSN5skuFQsx_dLEETuO_kq7YCyFr6LbqgXkCAEmBx=8VRdQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 798 bytes --]
On Mon, Feb 03, 2014 at 07:50:03PM +0100, Kristof Robot wrote:
> On Sat, Jan 11, 2014 at 4:08 PM, Andrei Gherzan <andrei@gherzan.ro> wrote:
> > Avoid a confusion when including thumb in TUNE_FATURES. In the curent behavior,
> > if I include thumb in TUNE_FATURES, ARM_THUMB_M_OPT will be "-marm" which makes
> > no sense for me as a default behavior.
>
> I agree that this is confusing, I actually fell for this - thinking I
> was using thumb instructions, while apparently I was not...
>
> Any update on this patch?
please test the patchset I've sent
http://lists.openembedded.org/pipermail/openembedded-core/2014-January/088665.html
it doesn't change the default, but it makes it easier to define thumb-only MACHINE
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2014-02-03 19:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-11 15:08 [PATCH 0/2] Cortex M3 tune fixes Andrei Gherzan
2014-01-11 15:08 ` [PATCH 1/2] feature-arm-thumb.inc: Use thumb instruction by default if TUNE_FEATURES thumb Andrei Gherzan
2014-01-11 15:10 ` Koen Kooi
2014-01-11 15:16 ` Andrei Gherzan
2014-01-11 18:23 ` Koen Kooi
2014-01-11 23:19 ` Martin Jansa
2014-02-03 18:50 ` Kristof Robot
2014-02-03 19:06 ` Martin Jansa [this message]
2014-01-11 15:08 ` [PATCH 2/2] tune-cortexm3.inc: Cortex-M3 doesn't support ARM instructions Andrei Gherzan
2014-01-13 18:16 ` [PATCH 0/2] Cortex M3 tune fixes Trevor Woerner
2014-01-13 18:25 ` Phil Blundell
2014-01-13 19:34 ` Trevor Woerner
2014-01-13 19:46 ` Koen Kooi
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=20140203190627.GH3698@jama \
--to=martin.jansa@gmail.com \
--cc=krirobo@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox