Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Phil Blundell <pb@pbcl.net>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 4/5] libav: upgrade to 9.18
Date: Fri, 29 May 2015 23:24:30 +0100	[thread overview]
Message-ID: <1432938270.2461.46.camel@pbcl.net> (raw)
In-Reply-To: <1528283.0UTgDEqc8E@peggleto-mobl.ger.corp.intel.com>

On Fri, 2015-05-29 at 16:28 +0100, Paul Eggleton wrote:
> Just for background, the reason I disabled the textrel check for x86 in 
> libav.inc was that I was able to determine based on quick research that 
> upstream deliberately doesn't enable -fPIC for x86 (32-bit) because apparently 
> it doesn't really work there. I honestly didn't check what the situation was 
> on 32-bit ARM; I probably should have done that at the time.

PIC is particularly problematic on x86 because it ties up %ebx.  This
represents 25% of the available general purpose registers which can
cause a measurable performance loss because of increased spilling, and
in the particular case of libav there is a lot of hand-written assembly
in the codecs which expects to be able to clobber that register.  It
certainly used to be the case that this code wouldn't compile at all
under -fpic.

The performance thing does apply to ARM as well but to a slightly lesser
extent.  The second problem probably doesn't affect ARM at all.  But,
personally, I would disable the textrel check and build without -fpic on
all platforms.

p.




  reply	other threads:[~2015-05-29 22:24 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-28  1:26 [PATCH 0/5] Fix CVE issues and add new libav recipe Kai Kang
2015-05-28  1:26 ` [PATCH 1/5] gpgme: fix CVE-2014-3564 Kai Kang
2015-05-28  1:26 ` [PATCH 2/5] grep: fix CVE-2015-1345 Kai Kang
2015-05-28  1:26 ` [PATCH 3/5] qt4: fix CVE issues Kai Kang
2015-05-28  6:12   ` Alexander Kanavin
2015-05-29  1:26     ` Kang Kai
2015-05-28  1:26 ` [PATCH 4/5] libav: upgrade to 9.18 Kai Kang
2015-05-28  7:14   ` Jussi Kukkonen
2015-05-28  8:18     ` Kang Kai
2015-05-28  8:38       ` Jussi Kukkonen
2015-05-28  8:47       ` Martin Jansa
2015-05-29  1:36         ` Kang Kai
2015-05-29 15:28           ` Paul Eggleton
2015-05-29 22:24             ` Phil Blundell [this message]
2015-05-30 13:17               ` Bernhard Reutner-Fischer
2015-05-28  1:26 ` [PATCH 5/5] libav: add recipe for 11 release series Kai Kang

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=1432938270.2461.46.camel@pbcl.net \
    --to=pb@pbcl.net \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=paul.eggleton@linux.intel.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