[Mesa-dev] [Bug 62357] llvmpipe: Fragment Shader with return in main causes back output

2013-03-22 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=62357 Roland Scheidegger srol...@vmware.com changed: What|Removed |Added Status|NEW |RESOLVED

[Mesa-dev] [Bug 62357] llvmpipe: Fragment Shader with return in main causes back output

2013-03-22 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=62357 --- Comment #14 from Roland Scheidegger srol...@vmware.com --- (In reply to comment #13) (In reply to comment #12) This is fixed with 5af7b45986d1b56c568ebe9c3a40d48853e2e9ff. Not sure if the testcase would be that useful as a piglit test.

[Mesa-dev] [Bug 62357] llvmpipe: Fragment Shader with return in main causes back output

2013-03-22 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=62357 --- Comment #15 from José Fonseca jfons...@vmware.com --- (In reply to comment #14) (In reply to comment #13) (In reply to comment #12) This is fixed with 5af7b45986d1b56c568ebe9c3a40d48853e2e9ff. Not sure if the testcase would be that

[Mesa-dev] [Bug 62357] llvmpipe: Fragment Shader with return in main causes back output

2013-03-15 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=62357 José Fonseca jfons...@vmware.com changed: What|Removed |Added CC||jfons...@vmware.com

[Mesa-dev] [Bug 62357] llvmpipe: Fragment Shader with return in main causes back output

2013-03-15 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=62357 --- Comment #6 from Brian Paul bri...@vmware.com --- My piglit test was with LLVM 3.2. -- You are receiving this mail because: You are the assignee for the bug. ___ mesa-dev mailing list

[Mesa-dev] [Bug 62357] llvmpipe: Fragment Shader with return in main causes back output

2013-03-15 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=62357 --- Comment #7 from Roland Scheidegger srol...@vmware.com --- After a quick look at the generated IR, it indeed seems broken. However, it is broken the opposite way, that is the early exit path is ok but if the path isn't taken it will pick zero

[Mesa-dev] [Bug 62357] llvmpipe: Fragment Shader with return in main causes back output

2013-03-15 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=62357 --- Comment #8 from Roland Scheidegger srol...@vmware.com --- Looks like we unconditionally return when we see a return not in a function. Some trivial attempt at fixing that seems to work but I'm not quite sure if it's right or if we need to do

[Mesa-dev] [Bug 62357] llvmpipe: Fragment Shader with return in main causes back output

2013-03-15 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=62357 --- Comment #9 from Brian Paul bri...@vmware.com --- Nice find, Roland. Do you want fix up my test case and put it into piglit? -- You are receiving this mail because: You are the assignee for the bug.

[Mesa-dev] [Bug 62357] llvmpipe: Fragment Shader with return in main causes back output

2013-03-15 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=62357 --- Comment #10 from Roland Scheidegger srol...@vmware.com --- Hmm I just noticed this doesn't actually work. Instead of not executing the code after the conditional, the result will now always be as if the condition passed, so the original

[Mesa-dev] [Bug 62357] llvmpipe: Fragment Shader with return in main causes back output

2013-03-15 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=62357 --- Comment #11 from Roland Scheidegger srol...@vmware.com --- Created attachment 76596 -- https://bugs.freedesktop.org/attachment.cgi?id=76596action=edit another testcase Here's another test case. With this one you can actually see if both

[Mesa-dev] [Bug 62357] llvmpipe: Fragment Shader with return in main causes back output

2013-03-14 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=62357 --- Comment #1 from Brian Paul bri...@vmware.com --- Created attachment 76543 -- https://bugs.freedesktop.org/attachment.cgi?id=76543action=edit piglit shader test to exercise the bug Do you happen to know which version of Mesa this is

[Mesa-dev] [Bug 62357] llvmpipe: Fragment Shader with return in main causes back output

2013-03-14 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=62357 --- Comment #2 from Brian Paul bri...@vmware.com --- (In reply to comment #1) Run with: bin/shader_runner tests/spec/glsl-1.10/execution/fs-return-in-main.shader_test -auto Err, just: bin/shader_runner fs-return-in-main.shader_test -auto If

[Mesa-dev] [Bug 62357] llvmpipe: Fragment Shader with return in main causes back output

2013-03-14 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=62357 --- Comment #3 from drag...@gmail.com --- (In reply to comment #1) Created attachment 76543 [details] piglit shader test to exercise the bug Do you happen to know which version of Mesa this is happening with? I can't tell from the gnome

[Mesa-dev] [Bug 62357] llvmpipe: Fragment Shader with return in main causes back output

2013-03-14 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=62357 --- Comment #4 from drag...@gmail.com --- FWIW this was using LLVM 3.2 as well. -- You are receiving this mail because: You are the assignee for the bug. ___ mesa-dev mailing list