On 21/05/12 15:52, Justin Ruggles wrote: > This will allow for easier implementation of Altivec functions in libraries > other than libavcodec. > --- > libavcodec/ppc/dsputil_altivec.c | 4 +- > libavcodec/ppc/fft_altivec.c | 5 +- > libavcodec/ppc/float_altivec.c | 2 +- > libavcodec/ppc/fmtconvert_altivec.c | 2 +- > libavcodec/ppc/gmc_altivec.c | 4 +- > libavcodec/ppc/h264_altivec.c | 4 +- > libavcodec/ppc/idct_altivec.c | 2 +- > libavcodec/ppc/int_altivec.c | 3 +- > libavcodec/ppc/mpegaudiodec_altivec.c | 2 +- > libavcodec/ppc/mpegvideo_altivec.c | 5 +- > libavcodec/ppc/types_altivec.h | 47 ------------- > libavcodec/ppc/util_altivec.h | 118 > --------------------------------- > libavcodec/ppc/vc1dsp_altivec.c | 5 +- > libavcodec/ppc/vp3dsp_altivec.c | 4 +- > libavcodec/ppc/vp8dsp_altivec.c | 4 +- > libavutil/ppc/types_altivec.h | 47 +++++++++++++ > libavutil/ppc/util_altivec.h | 118 > +++++++++++++++++++++++++++++++++
As long they are static inline function and macros shouldn't hurt at all. lu -- Luca Barbato Gentoo/linux http://dev.gentoo.org/~lu_zero _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
