All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phil Blundell <pb@pbcl.net>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v2 3/4] libav.inc: duplicate armv7a over-rides for armv7ve
Date: Tue, 12 Jan 2016 09:42:37 +0000	[thread overview]
Message-ID: <1452591757.1950.33.camel@pbcl.net> (raw)
In-Reply-To: <4E2CA517-1339-416B-832B-AB2EFF04CEE6@gmail.com>

On Mon, 2016-01-11 at 14:58 -0800, Khem Raj wrote:
> 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

I think -fno-tree-vectorize is just there as a workaround for old
compilers.  It sounds like you're saying that ffmpeg basically just
wants "-Ofast", and by implication it wants this on all architectures.
So in that case there is no need for a FULL_OPTIMIZATION override on
arm, let alone armv7a specifically.

Whether ffmpeg ought to be forcing its own FULL_OPTIMIZATION at all
versus leaving it up to the distro is another question.  Personally I
think that individual recipes have no business setting those variables,
and ffmpeg is no exception, but I don't have a particularly strong
opinion either way.

p.




  parent reply	other threads:[~2016-01-12  9:42 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
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 [this message]
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=1452591757.1950.33.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 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.