[x264-devel] [bug] asm operand has impossible constraints (x86)

[Henrik Gramner]

On Wed, Oct 28, 2015 at 4:57 PM, Sérgio Basto <sergio at serjux.com> wrote:
> Hi, Updating and correct my information
>
> On Seg, 2015-08-10 at 18:12 +0100, Sérgio Basto wrote:
>> > I can't tell if that is a bug in the build tools or in x264 and I
>> > don't have pratical experience in assembler.
>>
>> Strange , we build it on RPMFusion with  :
>> %ifarch i686 armv5tel armv6l
>>    --disable-asm \
>> %endif
>
> With i686 we in RPMFusion, do two builds one disabling asm and one with
> asm enabled, this second build is installed in /usr/lib/sse2 dir .
> From what I understood, i686 CPUs could be sse2-capable (or not) and for
> them we build with asm and install it in /usr/lib/sse2/ . Applications
> could detect if CPU is sse2-capable and if it is loads x264
> from /usr/lib/sse2/ .
>
>
> rpm -ql x264-libs.i686
> /usr/lib/libx264.so.142

Seems quite silly in my opinion considering that builds with asm are
>5 times faster and that the number of x86 machines without SSE2
should be well below 0.01% of the user base on modern distributions
nowadays, and it would be insanity to use such ancient and slow
machines for video encoding anyway.

If you still really want to supply a build without asm you should at
least put that one in a separate directory instead and have the
"normal" one be compiled with sane compilation flags.