From: Phil Blundell <philb@gnu.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] tune/armv7: Add -mthumb to TUNE_CCARGS
Date: Mon, 26 Mar 2012 15:37:06 +0100 [thread overview]
Message-ID: <1332772627.14363.1051.camel@phil-desktop> (raw)
In-Reply-To: <CAMKF1srb0tARAVLZKKvPoUCNQ5PVsBC-AEa0dLiw-3e7GaAEzA@mail.gmail.com>
On Mon, 2012-03-26 at 07:13 -0700, Khem Raj wrote:
> On Mon, Mar 26, 2012 at 4:21 AM, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> > On Mon, 2012-03-26 at 12:06 +0100, Phil Blundell wrote:
> >> On Mon, 2012-03-26 at 12:01 +0100, Richard Purdie wrote:
> >> > Looking at this file, if the above is true and armv7 can't do anything
> >> > other than thumb, shouldn't we just delete the non-thumb configurations
> >> > for "armv7"?
> >>
> >> It's not totally obvious to me that having a "lowest common denominator"
> >> configuration for ARMv7 is really all that valuable. In fact I would be
> >> slightly surprised if anybody is targetting ARMv7-M with OE at all.
> >> What's the use-case for that?
> >
> > I have no idea, it appears the file doesn't make a lot of sense...
> >
>
> on second thought I think we should delete this tune file since its
> somewhat useless.
Yes, agreed. It looks like Richard added it originally so, if he
doesn't know ( / has forgotten) what it's good for I would guess that
nobody does.
p.
next prev parent reply other threads:[~2012-03-26 14:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-25 16:48 [PATCH] tune/armv7: Add -mthumb to TUNE_CCARGS Khem Raj
2012-03-26 11:01 ` Richard Purdie
2012-03-26 11:06 ` Phil Blundell
2012-03-26 11:21 ` Richard Purdie
2012-03-26 14:13 ` Khem Raj
2012-03-26 14:37 ` Phil Blundell [this message]
2012-03-26 15:12 ` Richard Purdie
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=1332772627.14363.1051.camel@phil-desktop \
--to=philb@gnu.org \
--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.