From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 103743] Nier:Automata - "if" in fragment shader incorrectly evaluated, causes artifacts Date: Mon, 27 Nov 2017 20:42:08 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1142515779==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [IPv6:2610:10:20:722:a800:ff:fe98:4b55]) by gabe.freedesktop.org (Postfix) with ESMTP id A8C8D6E085 for ; Mon, 27 Nov 2017 20:42:08 +0000 (UTC) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============1142515779== Content-Type: multipart/alternative; boundary="15118153281.ABAd5.7463"; charset="UTF-8" --15118153281.ABAd5.7463 Date: Mon, 27 Nov 2017 20:42:08 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated https://bugs.freedesktop.org/show_bug.cgi?id=3D103743 --- Comment #6 from Nicolai H=C3=A4hnle --- Thanks. To give you an update, this is a super subtle control flow handling= bug in LLVM -- and the difference between the original shader and your modifica= tion at the LLVM input is merely that the sense of one branch is (correctly) inverted, leading LLVM down a subtly different path in the end. A sledge-hammer fix is quite simple, but I'm still thinking about how to ge= t a better fix which doesn't pessimize a bunch of cases. --=20 You are receiving this mail because: You are the assignee for the bug.= --15118153281.ABAd5.7463 Date: Mon, 27 Nov 2017 20:42:08 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated

Commen= t # 6 on bug 10374= 3 from Nicolai H=C3=A4hnle
Thanks. To give you an update, this is a super subtle control =
flow handling bug
in LLVM -- and the difference between the original shader and your modifica=
tion
at the LLVM input is merely that the sense of one branch is (correctly)
inverted, leading LLVM down a subtly different path in the end.

A sledge-hammer fix is quite simple, but I'm still thinking about how to ge=
t a
better fix which doesn't pessimize a bunch of cases.


You are receiving this mail because:
  • You are the assignee for the bug.
= --15118153281.ABAd5.7463-- --===============1142515779== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg== --===============1142515779==--