On 24/04/15 10:43, Olivier Fourdan wrote:
[...]
Yet, *not* setting _FORTIFY_SOURCE seems to work around the issue. I
find it weird the error is with the inlining of memcpy() ...
I'll double check on the gcc side and report back once I know more :)
Quick follow-up, I checked with Jakub and he
Hi Chris,
On 24/04/15 10:11, Chris Wilson wrote:
On Fri, Apr 24, 2015 at 09:43:37AM +0200, Olivier Fourdan wrote:
gcc generates an error at build time because it fails to inline some
functions:
blt.c: In function 'affine_blt':
blt.c:980:1: error: inlining failed in call to always_inline
On Fri, Apr 24, 2015 at 09:43:37AM +0200, Olivier Fourdan wrote:
> gcc generates an error at build time because it fails to inline some
> functions:
>
> blt.c: In function 'affine_blt':
> blt.c:980:1: error: inlining failed in call to always_inline
> 'bilinear_weight': optimization level att
On Fri, Apr 24, 2015 at 09:43:37AM +0200, Olivier Fourdan wrote:
> gcc generates an error at build time because it fails to inline some
> functions:
>
> blt.c: In function 'affine_blt':
> blt.c:980:1: error: inlining failed in call to always_inline
> 'bilinear_weight': optimization level att
gcc generates an error at build time because it fails to inline some
functions:
blt.c: In function 'affine_blt':
blt.c:980:1: error: inlining failed in call to always_inline
'bilinear_weight': optimization level attribute mismatch
bilinear_weight(pixman_fixed_t x)
blt.c:1164:7: error:
