All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 107581] Graphics Not Rendered Due to Missing 4.5 COMPAT Profile
Date: Tue, 21 Aug 2018 07:27:17 +0000	[thread overview]
Message-ID: <bug-107581-502-eIHRt0r545@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-107581-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1004 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=107581

Timothy Arceri <t_arceri@yahoo.com.au> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |t_arceri@yahoo.com.au

--- Comment #8 from Timothy Arceri <t_arceri@yahoo.com.au> ---
Created attachment 141209
  --> https://bugs.freedesktop.org/attachment.cgi?id=141209&action=edit
hack around preprocessor stringification

Ok I've taken a closer look and there is indeed new issues with this game
besides the existing ones.

Shaders include preprocessor stringification which is legal in C by not
specified in the GLSL spec e.g.

#define DOMAIN_PARAMS(dmn)         ROOT_SIG(DS) [domain(#dmn)]

I've hacked around that with the following patch but then hit further shaders
that fail to compile "unexpected LAYOUT_TOK"

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2657 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2018-08-21  7:27 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-15 12:46 [Bug 107581] Graphics Not Rendered Due to Missing 4.5 COMPAT Profile bugzilla-daemon
2018-08-15 12:55 ` bugzilla-daemon
2018-08-15 13:38 ` bugzilla-daemon
2018-08-15 13:40 ` bugzilla-daemon
2018-08-15 16:33 ` bugzilla-daemon
2018-08-20  5:18 ` bugzilla-daemon
2018-08-20  8:08 ` bugzilla-daemon
2018-08-21  2:10 ` bugzilla-daemon
2018-08-21  7:27 ` bugzilla-daemon [this message]
2018-08-21 10:52 ` bugzilla-daemon
2018-08-21 10:53 ` bugzilla-daemon
2018-08-21 11:13 ` bugzilla-daemon
2018-08-21 12:35 ` bugzilla-daemon
2018-08-21 12:49 ` bugzilla-daemon
2018-08-21 13:05 ` bugzilla-daemon
2018-08-22  1:30 ` bugzilla-daemon
2018-08-22  9:59 ` bugzilla-daemon
2018-08-25 17:17 ` bugzilla-daemon
2018-08-26  0:26 ` bugzilla-daemon
2018-08-26 14:01 ` bugzilla-daemon
2018-08-30  0:02 ` bugzilla-daemon
2018-09-06  2:33 ` bugzilla-daemon
2018-09-10 15:36 ` bugzilla-daemon

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=bug-107581-502-eIHRt0r545@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@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.