From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 93594] Flickering Shadows in The Talos Principle
Date: Thu, 18 Feb 2016 16:06:17 +0000 [thread overview]
Message-ID: <bug-93594-502-USfPMxpG1r@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-93594-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 737 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=93594
--- Comment #17 from Roland Scheidegger <sroland@vmware.com> ---
(In reply to Nicolai Hähnle from comment #16)
>
> One annoying aspect of this language is that one can reasonably read it as
> non-uniformity only being relevant for non-helper fragments. If a pixel quad
> is partial covered by the original primitive, and discard is used in a way
> that keeps the covered pixels but discard the helper ones, should
> derivatives be defined or not?
That's a good question... My interpretation would be that derivatives should be
undefined in this case if only because otherwise things get even more
complex...
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1578 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-02-18 16:06 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-05 15:16 [Bug 93594] Flickering Shadows in The Talos Principle bugzilla-daemon
2016-01-06 3:01 ` bugzilla-daemon
2016-01-06 18:59 ` bugzilla-daemon
2016-01-06 19:08 ` bugzilla-daemon
2016-01-07 8:58 ` bugzilla-daemon
2016-01-07 23:45 ` bugzilla-daemon
2016-01-07 23:50 ` bugzilla-daemon
2016-02-14 4:21 ` bugzilla-daemon
2016-02-17 1:17 ` bugzilla-daemon
2016-02-17 1:55 ` bugzilla-daemon
2016-02-17 16:51 ` bugzilla-daemon
2016-02-17 17:21 ` bugzilla-daemon
2016-02-17 21:12 ` bugzilla-daemon
2016-02-17 23:20 ` bugzilla-daemon
2016-02-18 1:17 ` bugzilla-daemon
2016-02-18 15:07 ` bugzilla-daemon
2016-02-18 15:25 ` bugzilla-daemon
2016-02-18 16:06 ` bugzilla-daemon [this message]
2016-02-19 10:17 ` bugzilla-daemon
2016-02-19 16:41 ` bugzilla-daemon
2016-02-19 20:05 ` bugzilla-daemon
2016-02-20 0:34 ` bugzilla-daemon
2016-02-20 10:17 ` bugzilla-daemon
2016-02-20 21:22 ` bugzilla-daemon
2016-02-22 1:00 ` bugzilla-daemon
2016-02-23 0:06 ` bugzilla-daemon
2016-02-25 21:46 ` bugzilla-daemon
2016-02-26 10:34 ` 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-93594-502-USfPMxpG1r@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;
as well as URLs for NNTP newsgroup(s).