Only SPIR-V & KHR_no_error Are Left Blocking OpenGL 4.6 In Mesa

[phoronix]

Phoronix: Only SPIR-V & KHR_no_error Are Left Blocking OpenGL 4.6 In Mesa

It's only the in-progress SPIR-V and KHR_no_error work left preventing the RadeonSI and Intel OpenGL drivers in Mesa from exposing OpenGL 4.6...

http://www.phoronix.com/scan.php?page=news_item&px=OpenGL-4.6-Easy-Extensions

[shmerl]

So now there will be a standard way to force anisotropic filtering for older games?

[smitty3268]

So now there will be a standard way to force anisotropic filtering for older games?

How is that what you took from the article?

No.

[Masush5]

So now there will be a standard way to force anisotropic filtering for older games?

Exposing a driver switch of some kind to force anisotropic filtering would also have been possible with EXT_texture_filtering_anisotropic, so i don't see how this would change anything.

[smartalgorithm]

too fast, too quick!
it's so good that nowadays one shouldn't be concerned much about the state of opengl in linux. it's just advancing very rapidly!

[Degra]

OpenGL 4.6 didn't add very much of substance anyways, besides SPIR-V of course. The addition of SPIR-V is amazing, especially for OpenGL - Vulkan familiarity.
GL no_error should be a nice little boost for performance, but has already been supported by most drivers anyways, now it's just an official standard of the API.

What I miss in 4.6:
Bindless texture
Shader draw parameters (Boo Intel for not supporting it)
Sparse texture

[shmerl]

Exposing a driver switch of some kind to force anisotropic filtering would also have been possible with EXT_texture_filtering_anisotropic, so i don't see how this would change anything.

Thing is, it's not exposed universally. For Radeonsi there is a specific switch:

R600_TEX_ANISO=16

But if that is now standard, why can't it be forceable for every driver?

[smitty3268]

Thing is, it's not exposed universally. For Radeonsi there is a specific switch:

R600_TEX_ANISO=16

But if that is now standard, why can't it be forceable for every driver?

Setting some random environment variable is not part of GL 4.6. That's still just some random implementation detail of the radeonsi driver.

As far as why other drivers can't do that - well, they can. But they could also have done that for years. Nothing has changed there - if they were going to create some environment variable exposing it to you, they probably already would have done so.