Out of curiosity, I tested the performance impact of --disable-asm on
i386 with gcc 7.3.
Without --disable-asm:
$ ffmpeg -i BigBuckBunny_320x180.mp4 -f null -benchmark -
[...]
bench: utime=5.136s
bench: maxrss=46660kB
$ ffmpeg -i big_buck_bunny_1080p_stereo.avi -f null -benchmark -
[...]
bench: u
On Sun, Feb 18, 2018 at 10:04 PM, Carl Eugen Hoyos wrote:
> (Since two bugs were reopened and the status was set to "forwarded":)
My modifications don't change anything about the wontfixness of the
situation. The objective was only to indicate that ffmpeg itself
would need to be changed before st
(Since two bugs were reopened and the status was set to "forwarded":)
Note that there will definitely be no "fix" within FFmpeg, simply
because the FFmpeg developers do not believe that there is a bug that
can be fixed.
If Debian believes there is an issue, it can be fixed quickly: Just
add --disa
