Re: [Mesa-dev] [PATCH] spirv: handle gl_SampleMask

2017-01-24 Thread Jason Ekstrand
Reviewed-by: Jason Ekstrand On Tue, Jan 24, 2017 at 4:48 AM, Iago Toral Quiroga wrote: > SPIR-V maps both gl_SampleMask and gl_SampleMaskIn to the same > builtin (SampleMask). The only way to tell which one we are dealing with > is to check if it is an

Re: [Mesa-dev] [PATCH] spirv: handle gl_SampleMask

2017-01-24 Thread Anuj Phogat
On Tue, Jan 24, 2017 at 4:48 AM, Iago Toral Quiroga wrote: > SPIR-V maps both gl_SampleMask and gl_SampleMaskIn to the same > builtin (SampleMask). The only way to tell which one we are dealing with > is to check if it is an input or an output. > > Fixes: >

Re: [Mesa-dev] [PATCH] spirv: handle gl_SampleMask

2017-01-24 Thread Lionel Landwerlin
Thanks, Reviewed-by: Lionel Landwerlin On 24/01/17 12:48, Iago Toral Quiroga wrote: SPIR-V maps both gl_SampleMask and gl_SampleMaskIn to the same builtin (SampleMask). The only way to tell which one we are dealing with is to check if it is an input or an

[Mesa-dev] [PATCH] spirv: handle gl_SampleMask

2017-01-24 Thread Iago Toral Quiroga
SPIR-V maps both gl_SampleMask and gl_SampleMaskIn to the same builtin (SampleMask). The only way to tell which one we are dealing with is to check if it is an input or an output. Fixes: dEQP-VK.pipeline.multisample_shader_builtin.sample_mask.write.* --- I am still waiting on Jenkins to report