From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 95085] Invalid sampling of second texture in fragment shader that have two samplers with different parameters. Date: Fri, 29 Apr 2016 23:27:02 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0335986197==" 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 AE2396E41B for ; Fri, 29 Apr 2016 23:27:02 +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 --===============0335986197== Content-Type: multipart/alternative; boundary="14619724211.6F4b60.30069"; charset="UTF-8" --14619724211.6F4b60.30069 Date: Fri, 29 Apr 2016 23:27:01 +0000 MIME-Version: 1.0 Content-Type: text/plain https://bugs.freedesktop.org/show_bug.cgi?id=95085 --- Comment #14 from Nicolai Hähnle --- I think I understand now where the bug is coming from, and I'm not sure if it's a driver or an application bug :) The trace uses glVertexAttribPointer instead of glVertexAttribIPointer to set up a vertex element that will consumed by an uint GLSL variable. I kind of suspect that that should be undefined behaviour, but I haven't found a corresponding spec reference. In any case, it looks like this causes different parts of the driver and the various auxiliary tools to disagree about whether the element should be treated as an int or as a float, and some conversion happens somewhere that makes it all go wrong... -- You are receiving this mail because: You are the assignee for the bug. --14619724211.6F4b60.30069 Date: Fri, 29 Apr 2016 23:27:01 +0000 MIME-Version: 1.0 Content-Type: text/html

Comment # 14 on bug 95085 from 
I think I understand now where the bug is coming from, and I'm not sure if it's
a driver or an application bug :)

The trace uses glVertexAttribPointer instead of glVertexAttribIPointer to set
up a vertex element that will consumed by an uint GLSL variable. I kind of
suspect that that should be undefined behaviour, but I haven't found a
corresponding spec reference.

In any case, it looks like this causes different parts of the driver and the
various auxiliary tools to disagree about whether the element should be treated
as an int or as a float, and some conversion happens somewhere that makes it
all go wrong...

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