After a little bit more testing, I think it would be a better idea to
file a bug report with nvidia complaining about the bug surrounding
the context creation. I think this is possibly a unreported regression
in the context creation and it should be safe to assume that the
description on how OpenGL
I think this is a case where using the forward compatibility bit may be a
reasonable fix. This is because it will always disable the compatibility
profile on core...
http://www.opengl.org/wiki/Core_And_Compatibility_in_Contexts
On Jun 18, 2014 4:43 PM, "Chad Versace" wrote:
> On Wed, Jun 18, 201
On Wed, Jun 18, 2014 at 12:29:09AM +0100, Emil Velikov wrote:
> On 17/06/14 23:50, Ian Romanick wrote:
> > On 06/16/2014 11:29 PM, Ilia Mirkin wrote:
> > This poses a problem for piglit. We want to make tests for things that
> > don't have GL_ARB_compatibility, but we can't actually ask for that.
On 17/06/14 23:50, Ian Romanick wrote:
> On 06/16/2014 11:29 PM, Ilia Mirkin wrote:
>> All the arb_shader_atomic_counters tests start with
>>
>> config.supports_gl_core_version = 31;
>>
>> However when I try to run them on the NVIDIA proprietary driver, I get:
>>
>> piglit: info: Requested
On 06/16/2014 11:29 PM, Ilia Mirkin wrote:
> All the arb_shader_atomic_counters tests start with
>
> config.supports_gl_core_version = 31;
>
> However when I try to run them on the NVIDIA proprietary driver, I get:
>
> piglit: info: Requested a OpenGL 3.1 Context, but the actual context
All the arb_shader_atomic_counters tests start with
config.supports_gl_core_version = 31;
However when I try to run them on the NVIDIA proprietary driver, I get:
piglit: info: Requested a OpenGL 3.1 Context, but the actual context
is a 3.1 context that exposes the GL_ARB_compatibility ex
