|Summary:||Mesa-utils -8.4 - glxinfo report has a blank value in GL_NUM_SHADING_LANGUAGE_VERSIONS subsection and also the aligniment below 4.3 seems not correct|
|Product:||Mesa||Reporter:||Arun Sivaraman <arunsivaramanneo>|
|Status:||RESOLVED MOVED||QA Contact:||mesa-dev|
|i915 platform:||i915 features:|
Description Arun Sivaraman 2018-02-28 03:57:30 UTC
Created attachment 137681 [details] glxinfo Hi The latest version of glxinfo displays a blank Value under GL_NUM_SHADING_LANGUAGE_VERSIONS sections, As per the report GL_NUM_SHADING_LANGUAGE_VERSIONS has 26 including the blank else it should be 25. Also, the alignment of GL_VERTEX_PROGRAM_ARB, GL_FRAGMENT_PROGRAM_ARB looks to be under 4.3. I am not sure if its correct. Please confirm
Comment 1 Brian Paul 2018-02-28 18:03:38 UTC
Regarding GL_NUM_SHADING_LANGUAGE_VERSIONS, the GL spec says that if GLSL 1.10 is supported, the name of the shading language is "" (an empty string). So it appears as a blank line. Yeah, that's kind of goofy. Maybe glxinfo should check for that and return something special, like "" or (110). What do you think? Regarding the GL_VERTEX_PROGRAM_ARB, GL_FRAGMENT_PROGRAM_ARB queries, that could certainly be improved. We already get most/all of those queries from the 2.0 and 3.2 lists. I'll see about cleaning that up.
Comment 2 Arun Sivaraman 2018-03-05 03:09:54 UTC
Apologies for the late reply, I didn't know about the blank value and ya it will be great if it can display 110 instead of blank. And also i did notice few more differences. I have nvidia GTX 850 and as per the latest it supports openGL 4.6 in both core and compat. profile. I thought the OpenGL limits for Core and Compat. will be same as both core and Compat. support 4.6 but i can see GL_ARB_IMAGING is not getting displayed in Core not sure if it is expected. Thanks for looking into it
Comment 5 Brian Paul 2018-03-05 16:52:24 UTC
What program is that in your screenshots? How does it relate to glxinfo -l? With my NVIDIA GPU, I see GL_ARB_imaging both in the core and compat profiles. I've got a few new patches for glxinfo/wglinfo. I'll cc you on the review requests.
Comment 6 Arun Sivaraman 2018-03-06 04:06:05 UTC
Thanks for the reply, well I have developed a front-end application to view glxinfo, vulkaninfo and clinfo reports, and i was trying to include both Compat. profile and Core profile limits to the report. I will attach my glxinfo -l report for my GTX 850m. Here is the front-end application https://github.com/arunsivaramanneo/GPU-Viewer, well Code is a mess and i am not a programmer but somehow it works.
Comment 7 Arun Sivaraman 2018-03-06 04:09:28 UTC
Created attachment 137810 [details] GTX850m_glxinfo-l
Comment 8 Brian Paul 2018-03-06 15:35:36 UTC
Sorry, but I don't have much time to look at your app and determine why you're not seeing GL_ARB_imaging in the core profile. Any comments on the glx/wglinfo patch series? If not, I'll push it in a day or so. Thanks.
Comment 9 Arun Sivaraman 2018-03-07 03:17:04 UTC
you don't have to use my app to see the glxinfo -l issue i mentioned before , i have already attached the glxinfo -l report of my gtx 850m. Other than this I haven't seen any other issues. Thanks
Comment 10 Brian Paul 2018-03-07 15:42:31 UTC
(In reply to Arun Sivaraman from comment #9) > you don't have to use my app to see the glxinfo -l issue i mentioned before > , i have already attached the glxinfo -l report of my gtx 850m. Other than > this I haven't seen any other issues. Thanks Looking at your 850mgtx.txt file, I see GL_ARB_imaging in the core profile extension list at line 82. For compat profile, I see it at line 542. With my GTX 750 I see the max convolution width/height=11 for both profiles. But for core profile, GL_MAX_COLOR_MATRIX_STACK_DEPTH=11 while compat profile reports GL_MAX_COLOR_MATRIX_STACK_DEPTH=2. I don't know why that is, but I don't think it's an issue. Maybe you can retest with the latest glxinfo built from git with my proposed patches. I'll actually push those patches now since they've been reviewed by others.
Comment 11 GitLab Migration User 2019-09-18 20:18:26 UTC
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/923.