Intel's Mesa Driver Should Have Compute Working For All Hardware Back To Ivy Bridge

[phoronix]

Phoronix: Intel's Mesa Driver Should Have Compute Working For All Hardware Back To Ivy Bridge

Francisco Jerez of Intel was pushing his SIMD32 changes into Mesa Git over night and benefits the driver's ARB_compute_shader support...

http://www.phoronix.com/scan.php?page=news_item&px=IVB-Compute-SIMD32

[haagch]

Uh... it was supposed to be disabled? I thought it was exposed on my ivy bridge GPU, but buggy.

For example McNopper's Example40 rendered this: https://www.youtube.com/watch?v=BCIh5MTDRNo (but e.g. Example30 and Example41 worked fine)
and I had opened this bug report: https://bugs.freedesktop.org/show_bug.cgi?id=94858
It's now fixed, possibly because of the new changes.


By the way, radeonsi still renders it with strange artifacts: https://youtu.be/yC4hf5LLAHM
Also broken on radeonsi:
Example30 renders a completely black window on radeonsi, but works on ivy bridge
Example42 renders a completely gray window on both radeonsi and ivy bridge

If anyone wants to test these examples: Clone https://github.com/McNopper/OpenGL, build glus from that repository and then build the example with these flags:

[COLOR=#000000]cd GLUS[/COLOR]  
cmake .
make
cd ..
cd Example40
gcc src/*.c -I ../GLUS/src/ -lGLEW -lGL -lm -L ../GLUS/ -l:libGLUS.a -lglfw
MESA_GL_VERSION_OVERRIDE=4.3 MESA_GLSL_VERSION_OVERRIDE=430 ./a.out

[treba]

Nice to see this as a ivybridge user! Is there some list somewhere were one can see how far the older intel generations are?
Like https://mesamatrix.net/ but for different generations?

Or does somebody know whats missing for ivybridge for ogl 4.0 - 4.3 support? Only the fp64 stuff or more?

[Tomin]

Nice to see this as a ivybridge user! Is there some list somewhere were one can see how far the older intel generations are?
Like https://mesamatrix.net/ but for different generations?

https://people.freedesktop.org/~imir...o/glxinfo.html It's not as frequently updated as Mesamatrix but it shows differences between generations.

[plonoma]

When is Intel going to enable GL_ARB_ES3_1_compatibility?
Intel worked so early on enabling all ES used extensions but haven't enabled the context creation while nvc0 and radeonsi have.

[Gusar]

When is Intel going to enable GL_ARB_ES3_1_compatibility?
Intel worked so early on enabling all ES used extensions but haven't enabled the context creation while nvc0 and radeonsi have.

The thing is, no Intel GPU actually has ES 3.1 yet. Gen7 is missing stencil texturing, gen8+ is missing compute shaders. However, the last set of SIMD32 patches is going through review right now, these will enable compute shaders on gen8+. But then, someone noticed that the spec for ES3_1_compatibility mentions GL 4.4 is required for it, so the enabling on nvc0 and radeonsi is not spec compliant

[Kayden]

The thing is, no Intel GPU actually has ES 3.1 yet. Gen7 is missing stencil texturing, gen8+ is missing compute shaders. However, the last set of SIMD32 patches is going through review right now, these will enable compute shaders on gen8+. But then, someone noticed that the spec for ES3_1_compatibility mentions GL 4.4 is required for it, so the enabling on nvc0 and radeonsi is not spec compliant

Actually, Gen8+ fully supported ES 3.1 in Mesa 11.2. We didn't need SIMD32 for that because the ES and Vulkan specs only require a work group size of 128, rather than the 1024 that OpenGL requires.

At this point, I don't see any reason not to enable ARB_ES3_1_compatibility.

[Stebs]

Is it possible that Gen7 (Ivy Bridge) supports GL_ARB_stencil_texturing (in a future, far far away), or asked in another way: what is the best OpenGL Version possible with Ivy Bridge, 4.2 or 4.3?

[plonoma]

The thing is, no Intel GPU actually has ES 3.1 yet. Gen7 is missing stencil texturing, gen8+ is missing compute shaders. However, the last set of SIMD32 patches is going through review right now, these will enable compute shaders on gen8+. But then, someone noticed that the spec for ES3_1_compatibility mentions GL 4.4 is required for it, so the enabling on nvc0 and radeonsi is not spec compliant

Could that someone have meant the extension ES3_1_compatibility needing some GL 4.4 extensions or functionality?

[smitty3268]

Could that someone have meant the extension ES3_1_compatibility needing some GL 4.4 extensions or functionality?

Nah, it was just the spec writers being lazy and requiring the current version of GL rather than figuring out what actually made sense as the minimum based on the functionality it exposes.

That kind of thing happens all the time, which is why they went ahead and enabled it in gallium.