From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 89069] Lack of grass in The Talos Principle on radeonsi (native\wine\nine) Date: Sat, 21 Feb 2015 13:36:07 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0554192746==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id B593E6E235 for ; Sat, 21 Feb 2015 05:36:07 -0800 (PST) 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 --===============0554192746== Content-Type: multipart/alternative; boundary="1424525767.45A0aDD31.25172"; charset="UTF-8" --1424525767.45A0aDD31.25172 Date: Sat, 21 Feb 2015 13:36:07 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable https://bugs.freedesktop.org/show_bug.cgi?id=3D89069 --- Comment #25 from Daniel Scharrer --- (In reply to Marek Ol=C5=A1=C3=A1k from comment #24) > I don't understand. Since setting the unsafe-fp-math attribute just for vertex shaders or just = for fragment shaders was both enough to trigger the bug (break grass and hide t= he GPU faults), I was just wondering if setting that attribute on one of the shader stages somehow also affected the optimization passes and/or codegen = for the other shader stages. > Shaders are whole programs. The OpenGL program object > has no meaning to gallium drivers. I'm really not that familiar with the Mesa / Gallium internals, so thanks f= or clearing that up. --=20 You are receiving this mail because: You are the assignee for the bug. --1424525767.45A0aDD31.25172 Date: Sat, 21 Feb 2015 13:36:07 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Commen= t # 25 on bug 89069<= /a> from Daniel Scharrer 
(In reply to Marek Ol=C5=A1=C3=A1k from comment #24)
> I don't understand.

Since setting the unsafe-fp-math attribute just for vertex shaders or just =
for
fragment shaders was both enough to trigger the bug (break grass and hide t=
he
GPU faults), I was just wondering if setting that attribute on one of the
shader stages somehow also affected the optimization passes and/or codegen =
for
the other shader stages.

> Shaders are whole programs. The OpenGL program o=
bject
> has no meaning to gallium drivers.

I'm really not that familiar with the Mesa / Gallium internals, so thanks f=
or
clearing that up.

You are receiving this mail because: =20=20=20=20=20=20
  • You are the assignee for the bug.
--1424525767.45A0aDD31.25172-- --===============0554192746== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHA6Ly9saXN0 cy5mcmVlZGVza3RvcC5vcmcvbWFpbG1hbi9saXN0aW5mby9kcmktZGV2ZWwK --===============0554192746==--