On Monday, April 06, 2015 10:01:16 AM Matt Turner wrote:
> On Sat, Apr 4, 2015 at 3:46 AM, Kenneth Graunke wrote:
> > Presumably no one has noticed this breakage because
> > ARB_transform_feedback3 isn't exposed on Haswell due to the ongoing
> > command streamer shenanigans, and ARB_gpu_shader5 is
On Sat, Apr 4, 2015 at 3:46 AM, Kenneth Graunke wrote:
> Presumably no one has noticed this breakage because
> ARB_transform_feedback3 isn't exposed on Haswell due to the ongoing
> command streamer shenanigans, and ARB_gpu_shader5 isn't exposed on
> Broadwell because we keep forgetting about it.
>
On Sat, Apr 04, 2015 at 03:46:33AM -0700, Kenneth Graunke wrote:
> Presumably no one has noticed this breakage because
> ARB_transform_feedback3 isn't exposed on Haswell due to the ongoing
> command streamer shenanigans, and ARB_gpu_shader5 isn't exposed on
> Broadwell because we keep forgetting ab
Presumably no one has noticed this breakage because
ARB_transform_feedback3 isn't exposed on Haswell due to the ongoing
command streamer shenanigans, and ARB_gpu_shader5 isn't exposed on
Broadwell because we keep forgetting about it.
Fixes 3 Piglit tests:
- spec/arb_gpu_shader5/emitstreamvertex_no
