Incorrect results returned by glGetProgramResourceiv for buffer objects in compute shader

[David_Eberly]

4th Generation Intel® Core™ Processors with Intel® HD Graphics 5000/4600/4400/4200
System Used:  Dell Inc. Precision T1700
CPU SKU: i7
GPU SKU: 4600
Processor Line: N/A
System BIOS Version: A16
CMOS settings: N/A
Graphics Driver Version: 10.18.15.4279 and 10.18.15.4281
GOP/VBIOS Version: N/A
Operating System: Windows 10 Pro 64-bit
OS Version: (10.0, Build 10586) (10586.th2_release.160104-1513)
API: OpenGL 4.3.0
Occurs on non-Intel GPUs?:  No (tested on NVIDIA and AMD)

Steps to Reproduce: I have provided a stand-alone Microsoft Visual Studio 2015 project that illustrates the problem.  The GLSL file CSFailToReference.glsl is compiled and linked successfully. The file has two buffer objects, each used by the compute shader.

Expected Results: Calls to glGetProgramResourceiv should return results that indicate the two buffer objects are referenced by the compute shader.

Actual Results:  The calls lead to results that indicate the two buffers are NOT referenced by the compute shader.

Additional Information: In other shaders, sometimes the buffers are referenced and sometimes not.  Initial investigations seemed to show that the failure to reference occurred when the buffer has an array of struct-type but references always occurred when the buffer has an array of native-type. However, I created a simple shader with a buffer having an array of struct-type but that buffer was reported as referenced.  It is not clear to me what the pattern is.

I can provide additional shaders where the problems do (or do not) occur.  Also, I attached the DxDiag output for my machine.

[David_Eberly]

I had attached files but then a back-button press in browser removed them.  Here they are.

[Michael_C_Intel2]

Hi Dave,

I have got this filed and am talking to our OpenGL driver team about this. I will let update you once our investigation begins.

-Michael

[David_Eberly]

Thank you, I appreciate your looking into this.

[Michael_C_Intel2]

Hi Dave,

We fixed the issues in the driver, the next driver release should have the fix in it. 

-Michael

[David_Eberly]

Hello Michael.  Much appreciated!  Thank you for letting me know.  Dave