More information about Intel crocus gen 6 to 7.5 in summary?

[stefano2734]

crocus starts with comments with gen 5+ in some features.
Gen 4 is oldest hardware in support, but there are no support of features of OpenGL 3.x+.

Crocus starts here in mesamatrix with Intel gen 6 Sandy bridge for this driver to gen 7.5 for haswell for openGL 3.3 and higher.
information of OpenGL level of gen 6, gen 7 and gen 7.5 ist not obvious in summation.

Gen 7.5 haswell is conformant with OpenGL 4.6+.
Gen 7 ivy bridge ist conformant with OpenGL 4.2+.
Gen 6 Sandy bridge is conformant with OpenGL 3.3+.
Gen 5 is conformant for OpenGL 2.x ?
Gen 4 is conformant for OpenGL 2.x ?

What more is possible?
openGL 2.x table for more information for Intel gen4 und gen5 and other hardware with OpenGL 2.x in Development to to Level OpenGL 3.x+.
conclusion: a logical system to comments is here needed for summary or manually by comments in summary.
And analog in OpenGL ES.

so a comment cell in table summary is possible and necessary. Manually or automated comments are here possible.
N/A is here not enough by more drivers with conformant to OpenGL 2.1 or OpenGL ES 3.0.

[MightyCreak]

Implementing logic around the hints (i.e. what's after the / after the drivers names) is bound to be very flaky.

It's not impossible, but it's a LOT of refactoring. It requires to implement a versioning scheme (so that the algorithm can understand that "6" is less than "7.5"), but also to understand that "gen6+" means "6 or more" while "gen8" means "only 8" (which does happen for GL_ARB_shader_ballot for instance), once that is done, you'll need to change the way drivers are displayed in the leaderboard, as now one driver (e.g. crocus), will have several entries in the leaderboard (e.g. crocus/gen6, crocus/gen7, crocus/gen7.5), which definitely won't help readability.

Also after all that, we'll need to tell apart what is a regular hint vs a hint about the drivers generation (i.e.what do you do about hints such as etnaviv/HALTI0, radeonsi/gfx9+, freedreno/a6xx, nvc0/gm200+, etc. which have completely different versioning schemes, or even worse: anv/gen11+ vs anv/gfx12.5+: it's the same driver, but a completely different versioning scheme, and there's also this: radv/gfx10.3- which means.. ??).

The file features.txt is far from a good source. It's a mere text file with a vague standard to organize the data, but I think it's too fragile to create complex algorithms based on these data.

It would be nice to be able to parse or compile the mesa code and get all the drivers features from there, but that is whole different system (that I don't even know if it's doable).