From: Phil Blundell <pb@pbcl.net>
To: Andre McCurdy <armccurdy@gmail.com>
Cc: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 3/3] glib.inc: limit ARM_INSTRUCTION_SET over-rides to armv4/armv5
Date: Thu, 03 Mar 2016 19:30:24 +0000 [thread overview]
Message-ID: <1457033424.587.4.camel@pbcl.net> (raw)
In-Reply-To: <CAJ86T=VFnc1rPssKouNWGbr-_WgyLKjau5hwn5-B4LiCh=jJUg@mail.gmail.com>
On Thu, 2016-03-03 at 11:11 -0800, Andre McCurdy wrote:
> All the good work and effort that Martin has been doing keeping the
> Thumb1 builds alive could then perhaps be redirected to testing Thumb2
> (or some other case which isn't covered by the default oe-core CI
> builds).
Yes, agreed. Given that, with modern processors and recent versions of
GCC, Thumb2 code is generally both smaller and faster than the
equivalent ARM binaries, it seems as though this is the configuration
that most users will want nowadays and consequently an important one to
test.
p.
prev parent reply other threads:[~2016-03-03 19:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-27 23:28 [PATCH 0/3] glib-2.0: minor fixes and updates Andre McCurdy
2016-01-27 23:28 ` [PATCH 1/3] glib-2.0: refresh configure-libtool.patch Andre McCurdy
2016-01-27 23:28 ` [PATCH 2/3] glib-2.0: drop add-march-i486-into-CFLAGS-automatically.patch Andre McCurdy
2016-02-01 22:23 ` Randy MacLeod
2016-02-01 22:44 ` Phil Blundell
2016-02-03 8:07 ` Huang, Jie (Jackie)
2016-01-27 23:28 ` [PATCH 3/3] glib.inc: limit ARM_INSTRUCTION_SET over-rides to armv4/armv5 Andre McCurdy
2016-03-03 13:02 ` Phil Blundell
2016-03-03 13:18 ` Martin Jansa
2016-03-03 14:00 ` Phil Blundell
2016-03-03 19:11 ` Andre McCurdy
2016-03-03 19:30 ` 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=1457033424.587.4.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