Kacper Michajłow 9066387b68 configure: build only the AltiVec and VSX files with their flags ...

The PPC SIMD code is selected at runtime, but configure added
-maltivec -mabi=altivec and -mvsx to CFLAGS, so GCC could emit AltiVec
and VSX instructions in any function. It does, so a default PPC32 build
crashes on CPUs without AltiVec. Collect the flags in ALTIVECFLAGS and
VSXFLAGS and add them only to the ALTIVEC-OBJS and VSX-OBJS objects and
to the header check of util_altivec.h. VSX is only enabled on
little-endian, where the AltiVec code loads and stores with VSX, so
there the AltiVec files get the VSX flags, as they did through CFLAGS.

Signed-off-by: Kacper Michajłow <kasper93@gmail.com>

2026-11-02 07:24:04 +00:00

..

cpu.c

libavutil/ppc: Remove mfspr-based AltiVec detection code for Linux

2026-04-01 04:33:44 +00:00

cpu.h

…

float_dsp_altivec.c

…

float_dsp_altivec.h

…

float_dsp_init.c

…

float_dsp_vsx.c

…

float_dsp_vsx.h

…

intreadwrite.h

…

Makefile

configure: build only the AltiVec and VSX files with their flags

2026-11-02 07:24:04 +00:00

timer.h

…

util_altivec.h

avcodec/ppc/vp8dsp: store the 16 pixel wide rows at any alignment

2026-08-12 20:05:32 +02:00