All of lore.kernel.org
 help / color / mirror / Atom feed
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 12:02:05 +0200	[thread overview]
Message-ID: <553A149D.3090100@redhat.com> (raw)
In-Reply-To: <553A0233.4020301@redhat.com>

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 confirmed this is a gcc issue:

    http://gcc.gnu.org/PR65873

So we should be all set, once this gcc bug is addressed.

Thanks!
Olivier

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

  reply	other threads:[~2015-04-24 10:02 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
2015-04-24 10:02     ` Olivier Fourdan [this message]
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=553A149D.3090100@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.