<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - GL42-CTS.gpu_shader_fp64.named_uniform_blocks fails"
href="https://bugs.freedesktop.org/show_bug.cgi?id=95505#c1">Comment # 1</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - GL42-CTS.gpu_shader_fp64.named_uniform_blocks fails"
href="https://bugs.freedesktop.org/show_bug.cgi?id=95505">bug 95505</a>
from <span class="vcard"><a class="email" href="mailto:itoral@igalia.com" title="Iago Toral <itoral@igalia.com>"> <span class="fn">Iago Toral</span></a>
</span></b>
<pre>So, our FS is not explicitly disabled, but it does not seem to run for any
fragments... from the description it seems that NVIDIA assigns a default value
to gl_Positon within the render region if the shader does not set it explicitly
(probably (0,0,0,1)?). I guess what we need to do to see if this is a bug in
the test or in the diver is check if there is anything in the GL spec that
mandates a specific value for gl_Position if none is set by the shader.</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>