All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olivier Fourdan <ofourdan@redhat.com>
To: "chunshan.zhu" <chunshan.zhu@gmail.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: build error with GCC5.1.1
Date: Mon, 18 May 2015 03:15:26 -0400 (EDT)	[thread overview]
Message-ID: <1962776957.330792.1431933326455.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <5559691B.3050508@gmail.com>

Hey,

> gcc5.1.1 generates an error at build time.
> 
> sna_accel.c: In function 'sna_poly_zero_line_blt':
> sna_accel.c:9207:10: warning: variable 'intersects' set but not used
> [-Wunused-but-set-variable]
>        bool intersects;
>            ^
> sna_accel.c:9107:6: warning: variable 'degenerate' set but not used
> [-Wunused-but-set-variable]
>    bool degenerate = true;
>        ^

Well, those are "unused variable warnings" so not an error. Could be easily fixed though.

>    CC       sna_cpu.lo
> In file included from /usr/include/string.h:635: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,

Right, this is a known issue in gcc 5.1, see here:

http://gcc.gnu.org/PR65873

The (easy) workaround is to avoid the "-Ofast" optimization.

E.g. something like that in src/sna/compiler.h:

--- a/src/sna/compiler.h
+++ b/src/sna/compiler.h
@@ -63,7 +63,7 @@
 #define sse4_2 __attribute__((target("sse4.2,sse2,fpmath=sse")))
 #endif
 
-#if HAS_GCC(4, 6) && defined(__OPTIMIZE__)
+#if HAS_GCC(4, 6) && !HAS_GCC(5, 0) && defined(__OPTIMIZE__)
 #define fast __attribute__((optimize("Ofast")))
 #else
 #define fast

But I do not think this is something suitable for upstream as the bug lies in gcc, so it's just a workaround until the issue is fixed in gcc.

HTH

Cheers,
Olivier.

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

      reply	other threads:[~2015-05-18  7:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-18  4:22 build error with GCC5.1.1 chunshan.zhu
2015-05-18  7:15 ` Olivier Fourdan [this message]

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=1962776957.330792.1431933326455.JavaMail.zimbra@redhat.com \
    --to=ofourdan@redhat.com \
    --cc=chunshan.zhu@gmail.com \
    --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.