[Mesa-dev] GLSL versions that don't match GL versions

Ilia Mirkin imirkin at alum.mit.edu
Sun Apr 26 17:58:23 PDT 2015


Hello,

Right now a driver has to be very careful about the GLSL version it
exposes, since it's computed separately from the GL version. The
main/version.c:compute_version code uses the consts->GLSLVersion as an
input, would there be any downside to having it also fix up the GLSL
version as well? For example, if I advertise a GLSLVersion 400, but
I'm missing, e.g., tess, or subroutines, or whatever, and the GL
version goes down to 3.3, is there any harm in fixing it up to be 330?

Among other things, _mesa_get_version does this for compat contexts,
so I guess it should be OK?

  -ilia


More information about the mesa-dev mailing list