Created attachment 75861 [details] test program See the test program for more info. When using specific enumerables with these commands, these commands return an error. glEnable(GL_MINMAX) glEnable(GL_MINMAX_EXT); glEnable(GL_HISTOGRAM); glConvolutionFilter1D(GL_CONVOLUTION_1D, GL_RGB8, 4, GL_RGB, GL_FLOAT, cf); glSeparableFilter2D(GL_SEPARABLE_2D, GL_RGB8, 2, 2, GL_RGB, GL_FLOAT, sf_a, sf_b); glColorTable(GL_COLOR_TABLE, GL_RGB8, 4, GL_RGB, GL_FLOAT, ct); I do not have the code yet to reproduce the last three, I need to convert it from ruby.
Mesa does not (or rather, no longer, it did at some point) support the clunky and legacy ARB_imaging subset. Therefore, trying to use functions or enumerants requiring that extension will indeed generate errors.
I'd still argue that this is a bug. If the extensions were removed, their implementation should be fully removed (as in, these functions, especially the EXT/ARB versions of them should be removed), instead of leaving some sort of a buggy shell, which can still be called (or at least can be tried to be called). So I'd just fully remove these, so there'd be no confusion.
(In reply to comment #2) > I'd still argue that this is a bug. If the extensions were removed, their > implementation should be fully removed (as in, these functions, especially > the EXT/ARB versions of them should be removed), instead of leaving some > sort of a buggy shell, which can still be called (or at least can be tried > to be called). So I'd just fully remove these, so there'd be no confusion. No this is not correct. The problem is there never was a separate ARB_imaging extension, this is (rather was) part of core but optionally supported. As such there's language in the spec which says you have to return invalid_enum for invalid operands and invalid_operation for unsupported functions belonging to this imaging subset.
Ah yes, I have found that bit later in the documentation. Thank you for clarification!
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.