From: sylvain.bertrand-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
To: Dawson Dias
<thexerothermicsclerodermoid+freedesktop-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Kent.Russel-5C7GfCeVMHo@public.gmane.org,
amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: Re: Cannot compile with GCC 8.1
Date: Sat, 12 May 2018 14:00:59 +0000 [thread overview]
Message-ID: <20180512140059.GA26918@freedom> (raw)
In-Reply-To: <20180510213402.GA6673@freedom>
On Thu, May 10, 2018 at 09:34:02PM +0000, sylvain.bertrand@gmail.com wrote:
> On Thu, May 10, 2018 at 10:27:12PM +0530, Dawson Dias wrote:
> > Wow they're just going to defer it untill GCC 9. So the kernel will be
> > unbuildable using GCC 8.x.
> > Pity.
>
> And recent llvm do not compile with gcc 7.3.0 because of the extreme complexity
> of the c++ syntax used in the latter... I was waiting for the official release
> of gcc 8.1 to see if the insane c++ syntax features used in llvm were finally
> implemented in g++, or the llvm guys do remove those which do only workin clang
> and not in g++.
> (gcc 8.1 pre-release was not generating correct code for GNU make).
>
> Really, an alternative "simple C" shader compiler would be more than welcome.
Recent llvm did workaround the 7.3.0 g++ advanced c++ bug.
--
Sylvain
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
next prev parent reply other threads:[~2018-05-12 14:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-10 16:57 Cannot compile with GCC 8.1 Dawson Dias
[not found] ` <CAFuwKQNiqL_aM=ZTXafej92nJVq1c9uXSd+h=9E24=J8U=041g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-05-10 21:34 ` sylvain.bertrand-Re5JQEeQqe8AvxtiuMwx3w
2018-05-12 14:00 ` sylvain.bertrand-Re5JQEeQqe8AvxtiuMwx3w [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-05-10 0:51 Dawson Dias
[not found] ` <CAFuwKQNqg4N9Op3Byp4BqBhDoOR7T8vu-Rt=Z_Z-qFPUyQ3P5g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-05-10 11:55 ` Russell, Kent
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=20180512140059.GA26918@freedom \
--to=sylvain.bertrand-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=Kent.Russel-5C7GfCeVMHo@public.gmane.org \
--cc=amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=thexerothermicsclerodermoid+freedesktop-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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.