| commit | b6c82f0a4de142a03ec07adbf85d9d2218487e45 | |
| author | Edward Wang <edward.c.wang@compdigitec.com> | |
| Thu, 26 Jul 2012 11:28:21 +0000 (26 07:28 -0400) | ||
| committer | Rafaël Carré <funman@videolan.org> | |
| Thu, 26 Jul 2012 11:30:36 +0000 (26 13:30 +0200) | ||
| tree | 4444285f460985af5885253644bed405f442c8dc | treesnapshot (tar.gz zip) |
| parent | 9cd6a20525e417e166fd82437fbf5a04216f5559 | commitdiff |
contrib: ffmpeg: Use -mincoming-stack-boundary=4
The issue here is that android-x86 doesn't guarantee an aligned stack, which means some of the inline asm functions will waste an extra register on realigning the stack.
libavcodec does however have stuff in place in all entrypoints that realign the stack on all calls into the library. If you build with --extra-cflags='-mincoming-stack-boundary=4', gcc assumes that the stack actually is aligned already, which the entry points ensure, so this inline asm builds fine.
Pointed-out-by: Martin Storsjö <martin@martin.st>
Signed-off-by: Rafaël Carré <funman@videolan.org>
The issue here is that android-x86 doesn't guarantee an aligned stack, which means some of the inline asm functions will waste an extra register on realigning the stack.
libavcodec does however have stuff in place in all entrypoints that realign the stack on all calls into the library. If you build with --extra-cflags='-mincoming-stack-boundary=4', gcc assumes that the stack actually is aligned already, which the entry points ensure, so this inline asm builds fine.
Pointed-out-by: Martin Storsjö <martin@martin.st>
Signed-off-by: Rafaël Carré <funman@videolan.org>
| contrib/src/ffmpeg/rules.mak | diffblobblamehistory |