Bug 94858 - McNopper Compute Shader Example40 broken on Intel
Summary: McNopper Compute Shader Example40 broken on Intel
Status: RESOLVED FIXED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/i965 (show other bugs)
Version: git
Hardware: Other All
: medium normal
Assignee: Jordan Justen
QA Contact: Intel 3D Bugs Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-04-07 13:11 UTC by Christoph Haag
Modified: 2016-05-28 13:07 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
apitrace (293.22 KB, application/octet-stream)
2016-04-07 13:11 UTC, Christoph Haag
Details

Description Christoph Haag 2016-04-07 13:11:58 UTC
Created attachment 122788 [details]
apitrace

I've been running these examples: https://github.com/McNopper/OpenGL

There don't seem to be build instructions... This works for me:

cd GLUS
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

Intel renders this brokenness: https://www.youtube.com/watch?v=BCIh5MTDRNo
radeonsi renders this, probably correctly: https://www.youtube.com/watch?v=Xlz36lyMFcg

Both videos are actually created with mesa git from the same attached apitrace on this hardware:

00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09)
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Wimbledon XT [Radeon HD 7970M] (rev ff)

There are no shader compile errors and mesa and apitrace report no GL errors I can see so I assume intel should be able to render it correctly.
Comment 1 Ian Romanick 2016-04-08 18:19:33 UTC
Jordan, can you take a look?
Comment 2 Christoph Haag 2016-05-28 13:07:28 UTC
Works now. Possibly because of the recent changes like
https://cgit.freedesktop.org/mesa/mesa/commit/?id=357495b94dad4101a5491ed30782574162de58db
(but I didn't test it)


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.