From: Phil Blundell <pb@pbcl.net>
To: Andre McCurdy <armccurdy@gmail.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] boost.inc: limit ARM_INSTRUCTION_SET over-rides to armv4/armv5
Date: Thu, 03 Mar 2016 16:32:44 +0000 [thread overview]
Message-ID: <1457022764.3476.46.camel@pbcl.net> (raw)
In-Reply-To: <1456361325-19298-1-git-send-email-armccurdy@gmail.com>
On Wed, 2016-02-24 at 16:48 -0800, Andre McCurdy wrote:
> The original over-ride dates back to 2009:
>
> http://git.openembedded.org/openembedded-core/commit/?id=43e94412c4
> 5b4b79485a64010c76d89b245bb235
>
> There are no obvious issues seen now when building boost in thumb2
> for Cortex A15.
Conceptually, this patch has the same armv6 problem as the glib-2.0 one
I mentioned earlier. But actually, boost seems to compile just fine as
Thumb-1 for armv5te, so I suspect that in this case the override is
just plain obsolete and could safely be deleted altogether.
p.
prev parent reply other threads:[~2016-03-03 16:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-25 0:48 [PATCH] boost.inc: limit ARM_INSTRUCTION_SET over-rides to armv4/armv5 Andre McCurdy
2016-03-03 16:32 ` Phil Blundell [this message]
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=1457022764.3476.46.camel@pbcl.net \
--to=pb@pbcl.net \
--cc=armccurdy@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