Re: [FFmpeg-devel] [PATCH v2 2/2] swscale: Fix AltiVec/VSX build with recent GCC

2019-08-11 Thread Daniel Kolesa
On Sun, Aug 11, 2019, at 21:39, Reimar Döffinger wrote: > On 11.08.2019, at 21:24, Reimar Döffinger wrote: > > > On 07.08.2019, at 19:39, Daniel Kolesa wrote: > > > >> The argument to vec_splat_u16 must be a literal. By making the > >> function always inline and marking the arguments const, gcc

Re: [FFmpeg-devel] [PATCH v2 2/2] swscale: Fix AltiVec/VSX build with recent GCC

2019-08-11 Thread Reimar Döffinger
On 11.08.2019, at 21:24, Reimar Döffinger wrote: > On 07.08.2019, at 19:39, Daniel Kolesa wrote: > >> The argument to vec_splat_u16 must be a literal. By making the >> function always inline and marking the arguments const, gcc can >> turn those into literals, and avoid build errors like: > >

Re: [FFmpeg-devel] [PATCH v2 2/2] swscale: Fix AltiVec/VSX build with recent GCC

2019-08-11 Thread Reimar Döffinger
On 07.08.2019, at 19:39, Daniel Kolesa wrote: > The argument to vec_splat_u16 must be a literal. By making the > function always inline and marking the arguments const, gcc can > turn those into literals, and avoid build errors like: Why marking the arguments const? If it depends on that it soun

[FFmpeg-devel] [PATCH v2 2/2] swscale: Fix AltiVec/VSX build with recent GCC

2019-08-07 Thread Daniel Kolesa
The argument to vec_splat_u16 must be a literal. By making the function always inline and marking the arguments const, gcc can turn those into literals, and avoid build errors like: swscale_vsx.c:165:53: error: argument 1 must be a 5-bit signed literal Fixes #7861. Signed-off-by: Daniel Kolesa