[Bug 99843] Geometry Shader - Incorrect Output

2019-09-18 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=99843 GitLab Migration User changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug 99843] Geometry Shader - Incorrect Output

2017-11-06 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=99843 --- Comment #15 from d...@jerber.co.uk --- I was reading about the R600 driver and came across a TODO page that suggested testing using piglit. I downloaded and compiled this. I ran the "shader.py" test and it gave the following results: skip:

[Bug 99843] Geometry Shader - Incorrect Output

2017-11-06 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=99843 --- Comment #14 from d...@jerber.co.uk --- The 4890 has a RV790 GPU. I've run the trace again and also see an error similar to the one Gert mentioned: 1639 Message api issue 1: FBO incomplete: no attachments and default width or height is 0

[Bug 99843] Geometry Shader - Incorrect Output

2017-11-05 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=99843 --- Comment #13 from d...@jerber.co.uk --- Hi, It is still a problem. I detailed the card in comment 8 (HD 4890). Could you advise what other information you would need about the GPU? Thanks. -- You are receiving this mail because: You are

[Bug 99843] Geometry Shader - Incorrect Output

2017-11-01 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=99843 --- Comment #12 from Ilia Mirkin --- No one has been able to reproduce, tried on various hardware including a Radeon 6870 (BARTS). Without more information, it's unlikely that anything will happen. At the very least (a)

[Bug 99843] Geometry Shader - Incorrect Output

2017-11-01 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=99843 --- Comment #11 from d...@jerber.co.uk --- Hi, Is it likely this will be looked into or are there no plans to look into issues for older cards? -- You are receiving this mail because: You are the assignee for the

[Bug 99843] Geometry Shader - Incorrect Output

2017-06-22 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=99843 --- Comment #10 from Gert Wollny --- Looks good on Barts (6870) (mesa-git 903e1047) that actually uses r600g. When replaying the trace I see an api issue message though: 1430: message: api issue 1: FBO incomplete: no

[Bug 99843] Geometry Shader - Incorrect Output

2017-02-19 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=99843 --- Comment #9 from Grazvydas Ignotas --- Also good on radeonsi (POLARIS10) and i965 (HSW). -- You are receiving this mail because: You are the assignee for the bug.___ dri-devel

[Bug 99843] Geometry Shader - Incorrect Output

2017-02-18 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=99843 smoki changed: What|Removed |Added Component|Drivers/Gallium/radeonsi|Drivers/Gallium/r600 --

[Bug 99843] Geometry Shader - Incorrect Output

2017-02-17 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=99843 --- Comment #8 from d...@jerber.co.uk --- The hardware is Radeon HD 4890. -- You are receiving this mail because: You are the assignee for the bug.___ dri-devel mailing list

[Bug 99843] Geometry Shader - Incorrect Output

2017-02-17 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=99843 --- Comment #7 from Ilia Mirkin --- FWIW it appears to render correctly on both nouveau (GK208) as well as i965 (SKL). -- You are receiving this mail because: You are the assignee for the

[Bug 99843] Geometry Shader - Incorrect Output

2017-02-17 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=99843 --- Comment #6 from Tom St Denis --- What hardware is this on? I wonder if it's a dup of 99850 (which was found on a Carrizo). -- You are receiving this mail because: You are the assignee for the

[Bug 99843] Geometry Shader - Incorrect Output

2017-02-17 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=99843 --- Comment #5 from d...@jerber.co.uk --- Created attachment 129697 --> https://bugs.freedesktop.org/attachment.cgi?id=129697=edit Trace -- You are receiving this mail because: You are the assignee for the

[Bug 99843] Geometry Shader - Incorrect Output

2017-02-17 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=99843 --- Comment #4 from d...@jerber.co.uk --- I created a minimal test program that simply draws the 3 polygons (12 sided). I have used apitrace with this test program to generate a trace and I'll upload this shortly. Thanks. -- You are receiving

[Bug 99843] Geometry Shader - Incorrect Output

2017-02-16 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=99843 --- Comment #3 from Ilia Mirkin --- https://github.com/apitrace/apitrace This can be used to record (and replay) all the GL commands sent down to the driver. -- You are receiving this mail because: You are the assignee

[Bug 99843] Geometry Shader - Incorrect Output

2017-02-16 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=99843 --- Comment #2 from d...@jerber.co.uk --- I've just tried with multiple draw calls using the same VBO and it appears this does also cause the error. However, it appears there has to be 3 or more calls to cause the error (1 and 2 calls produce the

[Bug 99843] Geometry Shader - Incorrect Output

2017-02-16 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=99843 --- Comment #1 from Nicolai Hähnle --- Interesting, thanks for the report. Is this really an issue of having separate VBOs, or does the issue also occur when you use separate draw calls with a single VBO? Or a single draw

[Bug 99843] Geometry Shader - Incorrect Output

2017-02-16 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=99843 Bug ID: 99843 Summary: Geometry Shader - Incorrect Output Product: Mesa Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW