On 10 January 2012 13:38, Christoph Bumiller <span dir="ltr"><<a href="mailto:e0425955@student.tuwien.ac.at">e0425955@student.tuwien.ac.at</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <div class="im">On 01/10/2012 10:09 PM, Dave Airlie wrote:<br> > On Tue, Jan 10, 2012 at 7:28 PM, Eric Anholt <<a href="mailto:eric@anholt.net">eric@anholt.net</a>> wrote:<br> >> On Tue, 10 Jan 2012 11:52:57 +0000, Dave Airlie <<a href="mailto:airlied@gmail.com">airlied@gmail.com</a>> wrote:<br> >>> From: Dave Airlie <<a href="mailto:airlied@redhat.com">airlied@redhat.com</a>><br> >>><br> >>> Things can get confused if you expose one without the other which can happen<br> >>> if you are missing one or two of the extensions (like say float textures).<br> >><br> >> Can you clarify what "things can get confused" means?<br> ><br> > Well piglit starts to fail in wierd and wonderful way, I just don't<br> > think we have any valid use cases for exposing GLSL1.30 without GL3<br> > and I'd like to enforce that.<br> ><br> <br> </div>Some tests only check for GLSL 1.3 and then use functions like<br> glUniform*ui that glew only sets up if GL_VERSION_3_0 and as a result<br> they call a NULL pointer.<br></blockquote><div><br>Personally I would call this a flaw in the piglit tests. If sloppy dependency checking in piglit tests is our only reason for making this change, then I'd rather fix the piglit tests rather than constrain what GLSL version Mesa can advertise. It was really useful for us in our GL 3.0 work on Sandy Bridge to be able to enable GLSL 1.30 support when it was ready, and not have to wait until we had all the components of GL 3.0 in place before we could start testing the GLSL 1.30 features.<br> <br>Paul<br></div></div>