From: Phil Blundell <pb@pbcl.net>
To: Khem Raj <raj.khem@gmail.com>
Cc: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCHv2][RFC] arch-armv7ve.inc: respect armv7a override as well
Date: Mon, 11 Jan 2016 19:52:00 +0000 [thread overview]
Message-ID: <1452541920.1950.27.camel@pbcl.net> (raw)
In-Reply-To: <4A8643CE-5D1C-45E5-8E89-891B18CDE7A6@gmail.com>
On Mon, 2016-01-11 at 11:10 -0800, Khem Raj wrote:
> So I was asking was what improvements do we get if we choose armv7ve as tune
> and I did not get any definitive answers.
If you compile with -march=armv7ve then you get the integer divide
instructions, which are not enabled under -march=armv7a.
>Why shouldnt we keep using armv7-a and tune the handful of apps to
>armv7ve where it is required.
That'd be a distro decision. I agree that if you are targetting a mix
of cores, some that have hardware div and some that don't, it may not be
sensible to compile everything twice and you might want to standardise
on armv7a as the least common denominator. But Cortex-A15 is
widespread, and I think people who select tune-cortexa15.inc would have
a reasonable expectation that it would, indeed, tune for the
instructions that their processor supports. That's not to say that it
necessarily needs to be a generic armv7ve tune of course.
> We should strive to reduce this tuning mayhem
> on arm especially.
I agree with this, though.
p.
next prev parent reply other threads:[~2016-01-11 19:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-08 12:36 [PATCH][RFC] arch-armv7ve.inc: respcet armv7a override as well Martin Jansa
2016-01-08 12:44 ` [PATCHv2][RFC] arch-armv7ve.inc: respect " Martin Jansa
2016-01-08 16:24 ` Andre McCurdy
2016-01-08 17:00 ` Martin Jansa
2016-01-08 18:24 ` Andre McCurdy
2016-01-08 20:44 ` Phil Blundell
2016-01-11 19:10 ` Khem Raj
2016-01-11 19:52 ` Phil Blundell [this message]
2016-01-11 20:03 ` Khem Raj
2016-01-11 19:53 ` Andre McCurdy
2016-01-08 20:13 ` Phil Blundell
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=1452541920.1950.27.camel@pbcl.net \
--to=pb@pbcl.net \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
/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