[Bug 102200] Wrong shader preprocessor string with Intel HD620 graphic card

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=102200

--- Comment #1 from Kenneth Graunke <kenneth at whitecape.org> ---
Hi Max,

I doubt this is a Mesa bug - it's more likely an application issue.

If the application is using a "Core Profile" OpenGL context, it will get OpenGL
4.5 and can use:

- GLSL 1.50 (#version 150)
- GLSL 3.30 (#version 330)
- GLSL 4.00 (#version 400)
- GLSL 4.10 (#version 410)
- GLSL 4.20 (#version 420)
- GLSL 4.30 (#version 430)
- GLSL 4.40 (#version 440)
- GLSL 4.50 (#version 450)
- GLSL ES 1.00 (#version 100)
- GLSL ES 3.00 (#version 300 es)
- GLSL ES 3.10 (#version 310 es)
- GLSL ES 3.20 (#version 320 es)

If the application is not specifically requesting a core profile context, it
will get a legacy GL context, which is OpenGL 3.0, which lets you use:

- GLSL 1.10 (#version 110 or no version line at all)
- GLSL 1.20 (#version 120)
- GLSL 1.30 (#version 130)
- GLSL ES 1.00 (#version 100)
- GLSL ES 3.00 (#version 300 es)
- GLSL ES 3.10 (#version 310 es)
- GLSL ES 3.20 (#version 320 es)

There is no GLSL 1.00 - "#version 100" actually refers to GLSL ES 1.00, which
is the shading language of OpenGL ES 2.0.  OpenGL can use these shaders because
we support GL_ARB_ES2_compatibility.

Likely the application expects to be able to use GLSL 1.50 in a legacy /
compatibility profile, while we only support it in core profile.

It should certainly be able to use GLSL 1.30 / #version 130 though, and the
fact that it doesn't work sounds like a bug in their fallback paths.

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-3d-bugs/attachments/20170814/68ecb2b8/attachment.html>