On Thu, 13 Oct 2016 23:58:45 +0200 Andreas Cadhalpun
<andreas.cadhal...@googlemail.com> wrote:
> Hi,
> 
> This only affects i386, where non-pic code is used for performance reasons.
> 
> I'm closing this wontfix bug now, because I think the topic is sufficiently
> documented in the lintian overrides, e.g.:
> # According to Debian policy [1], non position independent code is permitted
> # in a shared library on i386 and position independent code may have a
> # performance penalty, especially on i386.
> # Therefore -fPIC is not used by the upstream build system on i386.
> # 1: https://www.debian.org/doc/debian-policy/footnotes.html#f83
> libavcodec57 [i386]: shlib-with-non-pic-code usr/lib/i386*/libavcodec.so.*
> 
> Best regards,
> Andreas
> 
> 

Hi Andreas,

Do you know if upstream has re-evaluated this choice after gcc-5 fixed
one of the major performance issues with PIC on i386?

Source:
https://software.intel.com/en-us/blogs/2014/12/26/new-optimizations-for-x86-in-upcoming-gcc-50-32bit-pic-mode


Thanks,
~Niels

Reply via email to