Archives Discussions

[SingularZero]

Some weird behaviour i've noticed while testing my GLSL shader in AMD GPU shader Analyzer

Hey, today out of curiosity i've put my GLSL Vertex and Fragment shader to GPU Shader Analyzer while doing major changes in it.

And what i did get:

1)  varying mat4(or mat3) var_name; - causes "error(#174) Not enough data provided for construction constructor" in Fragment shader by just declaring it on every GPU listed in program. Even in empty shader.

2)  Arrays. I'm not sure but it looks like using varying array with int variable as iterator in cycle(Vertex Shader) makes it compile on about half of adapters. it says just "unexpected error" on 5xxx and 6xxx series. removing lines using arrays makes it compile on almost everything(except  x1xxx and older).

3) Radeon x1xxx and older - even empty shader won't compile on those, it shows N/A on every driver available.

4) Type casting. In some obscure cases(like "Array[int(some_float)] = 1.0") causes crash.

Conclusion: I'm scared. I'm really scared. If AMD GLSL compiler acts the same way on real adapters... That's not even funny, i didn't expect something like that even from AMD. Anyone can tell me that's just Shader Analyzer? Or i'm doing it just wrong?

[closed]

Yes, dude! I totally agree with you, and i can confirm, that:

1) all drivers later than 11.3 can't to compile long shaders with different functions, and fails with AMD favorite mistake - "unexpected error"

2) yes, in most cases expressions like:

float a = some_array[int(anything_float)];

leads to crash in driver, in function DrvBufferPresent()

3) usage of GLSL interfaces with special interpolation qualifiers leads to total ignoration of this qualifiers, example:

out s_gtof_OmniOuter
{
    flat float4 vViewPos3_fSqRange;            // this flat will not work!
    flat float4 vColor3_fInvRange;
    float3 vRay3;
    float3 vProjUv3;
}
v_OmniOuter;

4) glClearBuffer behavior is not corresponding OpenGL 3.3/4.1 specification

P.S. I HATE AMD! I'm a graphics programmer, and i can't to do my job, because with every new driver i first of all do a lot of test... and what i see, nvidia - all works fine, amd/ati - crash or undefined behavior

IM SO ANGRY!

AMD WINDOWS DRIVER TEAM - THE WORST DRIVER TEAM EVER!

[plohrmann]

If possible, please submit your shaders to gputools.support@amd.com so that we can test with them. Thank you.

[closed]

Thank you for the reply!

First of all i appologies - this is error occurs not in Shder Analyzer, but in latest drivers. I think, that i prepare some small executables for reproducing this crashes in a short time (: