From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 98307] "st/glsl_to_tgsi: explicitly track all input and output declaration" broke flightgear colors on rs780
Date: Tue, 18 Oct 2016 15:37:51 +0000 [thread overview]
Message-ID: <bug-98307-502-eGWxBUoI7A@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-98307-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 671 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=98307
--- Comment #2 from Nicolai Hähnle <nhaehnle@gmail.com> ---
Created attachment 127378
--> https://bugs.freedesktop.org/attachment.cgi?id=127378&action=edit
wild guess
I cannot reproduce this on either llvmpipe or Redwood, and I don't have a
pre-Evergreen card anymore.
My best guess is that the driver gets confused because the order of input and
output declarations is changed. Does the attached patch help?
If that doesn't help, could you please attach logs with R600_DEBUG=vs,ps both
before and after the bad commit?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1775 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
next prev parent reply other threads:[~2016-10-18 15:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-18 12:26 [Bug 98307] "st/glsl_to_tgsi: explicitly track all input and output declaration" broke flightgear colors on rs780 bugzilla-daemon
2016-10-18 12:41 ` bugzilla-daemon
2016-10-18 15:37 ` bugzilla-daemon [this message]
2016-10-18 15:59 ` bugzilla-daemon
2017-04-28 9:03 ` 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-98307-502-eGWxBUoI7A@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox