From: Khem Raj <raj.khem@gmail.com>
To: Phil Blundell <pb@pbcl.net>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v2 3/4] libav.inc: duplicate armv7a over-rides for armv7ve
Date: Mon, 11 Jan 2016 14:58:09 -0800 [thread overview]
Message-ID: <4E2CA517-1339-416B-832B-AB2EFF04CEE6@gmail.com> (raw)
In-Reply-To: <1452210004.2002.129.camel@pbcl.net>
[-- Attachment #1: Type: text/plain, Size: 1496 bytes --]
> On Jan 7, 2016, at 3:40 PM, Phil Blundell <pb@pbcl.net> wrote:
>
> On Thu, 2016-01-07 at 14:29 -0800, Andre McCurdy wrote:
>> FULL_OPTIMIZATION_armv7a = "-fexpensive-optimizations -fomit-frame-pointer -O4 -ffast-math"
>> +FULL_OPTIMIZATION_armv7ve = "-fexpensive-optimizations -fomit-frame-pointer -O4 -ffast-math"
>
O4 ? may be just replace this whole thing with -Ofast now a days
-fexpensive-optimizations is enabled at -O2,-O3 anyway same for fomit-frame-pointer and -Ofast turns on
feast-match on top of -O3
> I wonder if this would be better as just FULL_OPTIMIZATION_arm. That
> said, the OPTIMIZATION variables are primarily distro knobs and it's not
> entirely clear that individual packages ought to be overriding them at
> all.
>
> Does anybody know whether there is any actual science behind the use of
> those flags on armv7a specifically?
it came into ffmpeg circa 2008 and proliferated into related components primarily to support vectorization and neon
which was quite nascent for ARM architecture in those days in gcc. Today if you were to configure libav with default options
then it uses mainly -fomit-frame-pointer-O3 -fno-math-errno -fno-signed-zeros -fno-tree-vectorize
which is primarily -Ofast -fno-tree-vectorize
>
> p.
>
>
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 211 bytes --]
next prev parent reply other threads:[~2016-01-11 22:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-07 22:29 [PATCH v2 0/4] fixup armv7a over-rides for armv7ve Andre McCurdy
2016-01-07 22:29 ` [PATCH v2 1/4] valgrind: don't restrict to armv7a Andre McCurdy
2016-01-07 22:29 ` [PATCH v2 2/4] gcc-configure-common.inc: duplicate armv7a over-ride for armv7ve Andre McCurdy
2016-01-07 23:34 ` Phil Blundell
2016-01-08 1:16 ` Andre McCurdy
2016-01-07 22:29 ` [PATCH v2 3/4] libav.inc: duplicate armv7a over-rides " Andre McCurdy
2016-01-07 23:40 ` Phil Blundell
2016-01-08 2:29 ` Andre McCurdy
2016-01-11 22:58 ` Khem Raj [this message]
2016-01-11 23:07 ` Richard Purdie
2016-01-11 23:18 ` Khem Raj
2016-01-11 23:18 ` Andre McCurdy
2016-01-12 9:42 ` Phil Blundell
2016-01-12 16:26 ` Khem Raj
2016-01-07 22:29 ` [PATCH v2 4/4] libpostproc: " Andre McCurdy
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=4E2CA517-1339-416B-832B-AB2EFF04CEE6@gmail.com \
--to=raj.khem@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=pb@pbcl.net \
/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