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 12:26:42 +0000 [thread overview]
Message-ID: <bug-98307-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 829 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=98307
Bug ID: 98307
Summary: "st/glsl_to_tgsi: explicitly track all input and
output declaration" broke flightgear colors on rs780
Product: Mesa
Version: git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r600
Assignee: dri-devel@lists.freedesktop.org
Reporter: marvin24@gmx.de
QA Contact: dri-devel@lists.freedesktop.org
Created attachment 127376
--> https://bugs.freedesktop.org/attachment.cgi?id=127376&action=edit
screenshot of broken colors
Mesa commit 777dcf81b.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2400 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 reply other threads:[~2016-10-18 12:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-18 12:26 bugzilla-daemon [this message]
2016-10-18 12:41 ` [Bug 98307] "st/glsl_to_tgsi: explicitly track all input and output declaration" broke flightgear colors on rs780 bugzilla-daemon
2016-10-18 15:37 ` bugzilla-daemon
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@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.