On Mon, Jun 06, 2016 at 02:40:15PM -0700, Matt Turner wrote:
> 4.30 removes gl_FragColor. In debugging bug 96320, I found it useful to
> replace gl_FragColor with a user-defined varying so that the tests could
> be run under GLSL 4.30.
Reviewed-by: Topi Pohjolainen
On Monday, June 6, 2016 3:56:09 PM PDT Mark Janes wrote:
> Kenneth Graunke writes:
>
> > The new ARB_vertex_attrib_64bit tests specify integer uniform values
> > as hex, such as 0xc21620c5. As an integer value, this is beyond LONG_MAX
> > on 32-bit systems. The intent is
Kenneth Graunke writes:
> The new ARB_vertex_attrib_64bit tests specify integer uniform values
> as hex, such as 0xc21620c5. As an integer value, this is beyond LONG_MAX
> on 32-bit systems. The intent is to parse it as an unsigned hex value and
> bitcast it.
>
>
In order to emit a color for each vertex, we need to move fs_color
inside the loop because EmitVertex() will invalidate all previous
output writes, and there is an interpolated varying in the fragment
shader.
Signed-off-by: Samuel Pitoiset
---
4.30 removes gl_FragColor. In debugging bug 96320, I found it useful to
replace gl_FragColor with a user-defined varying so that the tests could
be run under GLSL 4.30.
---
.../execution/aggregate-dynamic-initializer-matrix.shader_test | 3 ++-
The new ARB_vertex_attrib_64bit tests specify integer uniform values
as hex, such as 0xc21620c5. As an integer value, this is beyond LONG_MAX
on 32-bit systems. The intent is to parse it as an unsigned hex value and
bitcast it.
However, we still need to handle parsing values with negative
The new ARB_vertex_attrib_64bit tests specify integer vertex attributes
with hex values, such as 0xc21620c5. As an integer value, this is
beyond LONG_MAX on 32-bit systems. The intent is to parse it as an
unsigned hex value and bitcast it.
However, we still need to handle parsing values with
Acked-by: Matt Turner
___
Piglit mailing list
Piglit@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/piglit
On 02/06/16 00:50, Dylan Baker wrote:
This currently doesn't test building piglit (the C/C++ code), only the
python bits, and only the framework, not the generators. It's probably
worth adding support for all of that, but it's a more involved project,
and I'm just trying to not break the