From: Olivier Fourdan <ofourdan@redhat.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [RFC PATCH] sna: Fix build with gcc 5.0
Date: Fri, 24 Apr 2015 10:43:31 +0200 [thread overview]
Message-ID: <553A0233.4020301@redhat.com> (raw)
In-Reply-To: <20150424081126.GA599@nuc-i3427.alporthouse.com>
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
>> 'bilinear_weight': optimization level attribute mismatch
>
> Does this mean anything more specific (than just it not being able to
> inline)?
>
>> Note: It could be a gcc bug, I am not sure, I don't know enough of
>> gcc internals to tell, that's why I post this patch as "RFC".
>
> Since bilinear_weight() is trivial and bilinear_interpolation() is only
> called from one location, I wonder what is up?
Humm, that looks definitely dodgy, now the build fails a bit further
when _FORTIFY_SOURCE is set to 2:
In file included from /usr/include/string.h:639:0,
from /usr/include/xorg/os.h:53,
from /usr/include/xorg/misc.h:115,
from /usr/include/xorg/xf86str.h:37,
from sna.h:43,
from blt.c:32:
blt.c: In function 'memcpy_from_tiled_x__swizzle_9_10_11':
/usr/include/bits/string3.h:50:42: error: inlining failed in call to
always_inline 'memcpy': optimization level attribute mismatch
__NTH (memcpy (void *__restrict __dest, const void *__restrict __src,
^
blt.c:474:1314: error: called from here
In file included from /usr/include/string.h:639:0,
from /usr/include/xorg/os.h:53,
from /usr/include/xorg/misc.h:115,
from /usr/include/xorg/xf86str.h:37,
from sna.h:43,
from blt.c:32:
/usr/include/bits/string3.h:50:42: error: inlining failed in call to
always_inline 'memcpy': optimization level attribute mismatch
__NTH (memcpy (void *__restrict __dest, const void *__restrict __src,
^
blt.c:474:1605: error: called from here
In file included from /usr/include/string.h:639:0,
from /usr/include/xorg/os.h:53,
from /usr/include/xorg/misc.h:115,
from /usr/include/xorg/xf86str.h:37,
from sna.h:43,
from blt.c:32:
/usr/include/bits/string3.h:50:42: error: inlining failed in call to
always_inline 'memcpy': optimization level attribute mismatch
__NTH (memcpy (void *__restrict __dest, const void *__restrict __src,
^
blt.c:474:1865: error: called from here
Makefile:650: recipe for target 'blt.lo' failed
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 :)
Cheers,
Olivier
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-04-24 8:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-24 7:43 [RFC PATCH] sna: Fix build with gcc 5.0 Olivier Fourdan
2015-04-24 8:11 ` Chris Wilson
2015-04-24 8:43 ` Olivier Fourdan [this message]
2015-04-24 10:02 ` Olivier Fourdan
2015-04-24 8:39 ` Chris Wilson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=553A0233.4020301@redhat.com \
--to=ofourdan@redhat.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.