FFmpeg

298MB

Tree: b56adc7842

Author	SHA1	Message	Date
Måns Rullgård	9a83adaf34	arm: Avoid using the movw instruction needlessly This fixes building for ARM11 without Thumb2. Signed-off-by: Martin Storsjö <martin@martin.st>	14 years ago
Mans Rullgard	8986fddc2b	ARM: allow building in Thumb2 mode Signed-off-by: Mans Rullgard <mans@mansr.com>	14 years ago
Martin Aumüller	b1eb7a1204	arm: properly mark external symbol call Surround memset and ff_vp8_dct_cat_prob by X() in order to fix iOS build Includes patch by Luca Barbato <lu_zero@gentoo.org>. Signed-off-by: Luca Barbato <lu_zero@gentoo.org>	14 years ago
Aurelien Jacobs	13d4ec844a	cosmetics: alignment	14 years ago
pin xue	05c062e9da	replace movw instruction in ac3dsp_armv6.S AS libavcodec/arm/ac3dsp_armv6.o ffmpeg-src/libavcodec/arm/ac3dsp_armv6.S: Assembler messages: ffmpeg-src/libavcodec/arm/ac3dsp_armv6.S:40: Error: selected processor does not support `movw r8,#0x1fe0' make[1]: *** [libavcodec/arm/ac3dsp_armv6.o] Error 1 MOVW is ARMv7 way to load constant: * movw, or move wide, will move a 16-bit constant into a register, implicitly zeroing the top 16 bits of the target register. * movt, or move top, will move a 16-bit constant into the top half of a given register without altering the bottom 16 bits To load 32 bit constant, movw lower16; movt upper16; is better than ldr if available, because: While this approach takes two instructions, it does not require any extra space to store the constant so both the movw/movt method and the ldr method will end up using the same amount of memory. Memory bandwidth is precious in and the movw/movt approach avoids an extra read on the data side, not to mention the read could have missed the cache. But here it is armv6 optimization, so that we have to use ldr. Signed-off-by: Michael Niedermayer <michaelni@gmx.at>	14 years ago
Mans Rullgard	182826c884	ac3: armv6 optimised bit_alloc_calc_bap Signed-off-by: Mans Rullgard <mans@mansr.com>	14 years ago

4 Commits (b56adc784288bdbe5e34e581e8081b51a2a3eb5f)