https://bugs.freedesktop.org/show_bug.cgi?id=66731
GitLab Migration User changed:
What|Removed |Added
Resolution|--- |MOVED
Status|NEW
https://bugs.freedesktop.org/show_bug.cgi?id=66731
--- Comment #2 from Stefano Teso ---
Thanks for the quick response.
I just wanted to note that the glitch is still there with llvm 3.4 trunk.
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
https://bugs.freedesktop.org/show_bug.cgi?id=66731
--- Comment #2 from Stefano Teso ---
Thanks for the quick response.
I just wanted to note that the glitch is still there with llvm 3.4 trunk.
--
You are receiving this mail because:
You are the assignee for the bug.
___
https://bugs.freedesktop.org/show_bug.cgi?id=66731
--- Comment #1 from Vadim Girlin ---
Created attachment 82247
--> https://bugs.freedesktop.org/attachment.cgi?id=82247&action=edit
shader dump
Looks like it's llvm backend's issue, I'm attaching the dump of the failing
shader.
As far as I kno
https://bugs.freedesktop.org/show_bug.cgi?id=66731
--- Comment #1 from Vadim Girlin ---
Created attachment 82247
--> https://bugs.freedesktop.org/attachment.cgi?id=82247&action=edit
shader dump
Looks like it's llvm backend's issue, I'm attaching the dump of the failing
shader.
As far as I kno