On 20 January 2012 11:57, Eric Anholt <span dir="ltr"><<a href="mailto:eric@anholt.net">eric@anholt.net</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Thu, 19 Jan 2012 18:27:12 -0800, Paul Berry <<a href="mailto:stereotype441@gmail.com">stereotype441@gmail.com</a>> wrote:<br>
> See <a href="https://bugs.freedesktop.org/show_bug.cgi?id=40865#c9" target="_blank">https://bugs.freedesktop.org/show_bug.cgi?id=40865#c9</a><br>
<br>
I don't like our bugs/ directory -- how many of the tests we write are<br>
in response to "bugs"? But especially how we (myself included) have<br>
named them according to the bug number. When it fails, you don't even<br>
know if it's probably a GLSL bug or a readpixels segfault or a state<br>
tracking bug or what. I'm thinking maybe call this<br>
"glsl-struct-assignment-1" or something under shaders/ at least.<br>
</blockquote></div><br>Ok, I can live with that. I think I'll rename it to<br><br>tests/spec/glsl-1.20/execution/vs-assign-varied-struct.shader_test<br><br>Which reminds me...I ought to test this in the fragment shader too. I'll send a revised patch.<br>