<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [Regression, bisected] spec.ext_transform_feedback.structs_gles3 tests fail"
href="https://bugs.freedesktop.org/show_bug.cgi?id=90961#c3">Comment # 3</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [Regression, bisected] spec.ext_transform_feedback.structs_gles3 tests fail"
href="https://bugs.freedesktop.org/show_bug.cgi?id=90961">bug 90961</a>
from <span class="vcard"><a class="email" href="mailto:idr@freedesktop.org" title="Ian Romanick <idr@freedesktop.org>"> <span class="fn">Ian Romanick</span></a>
</span></b>
<pre>(In reply to Timothy Arceri from <a href="show_bug.cgi?id=90961#c2">comment #2</a>)
<span class="quote">> It seems desktop specs before 4.40 used the same line as the ES 3.0 spec,
> but the test don't fail to compile on closed source Nvidia drivers (although
> they do seem to fail execution).
>
> However arrays of structs or structs that contain arrays or structs are
> clearly allowed from 4.40 on.
>
> My head hurts, Ian please help.</span >
Basically, the ES group interpreted the line differently than the desktop
group. There was discussion about this while bringing arrays-of-arrays to ES,
and that precipitated the clarification in the desktop spec.
Frankly, unless there is a conformance test or a dEQP test that requires the
restricted behavior, I'd rather not start enforcing it. Since the code is
already landed, it's probably not worth the effort to undo it. My best guess
is that we should just remove the gles3 tests that require out-of-spec
behavior.
Also... if a patch series is known to cause a big pile of tests to fail (you
did run piglit before pushing, right?), that needs to be resolved first.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>