Shader crash on 4th-5th gen GPUs

[Michael_B_14]

Hey, I'm writing shaders in opengl 1.20 for a mod for minecraft which allows the usage of shaders.
However those shaders crash/fails to compile on 4th and 5th gen chipsets with drivers newer than .4080.
They work absolutely fine when using .4080.

Tested on:
Intel HD 4600, every driver after 4080 crashes / fails to compile the shaders
Intel HD 5500, every driver after 4080 crashes / fails to compile the shaders

OS:
Windows 7 x64 SP1
(OS doesn't seem to matter tho)

Crash doesn't occur on 2nd nor 3rd gen chipsets.
Tested on:
Intel HD 4000, driver 4226
Intel HD Graphics (bay trail mobile), driver 4226

Intel HD 4600 logs can be found here:
https://dl.dropboxusercontent.com/u/14381275/Sildur_1.07_0.94_Test_Intel_HD4600_10.18.14.4080_Working.txt <- 4080, works fine
https://dl.dropboxusercontent.com/u/14381275/Sildur_1.07_0.94_Test_Intel_HD4600_10.18.14.4139_Crash.txt <- 4139, compiling errors
https://dl.dropboxusercontent.com/u/14381275/Sildur_1.07_0.94_Test_Intel_HD4600_10.18.14.4206_Crash.txt <- 4206, compiling errors
https://dl.dropboxusercontent.com/u/14381275/Sildur_1.07_0.94_Test_Intel_HD4600_10.18.14.4222_Crash.txt <- 4222, compiling errors

Intel HD 5500 logs can be found here:
https://dl.dropboxusercontent.com/u/14381275/Sildur_1.07_0.94_Test_Intel_HD5500_10.18.14.4080_Working.txt <- 4080, works fine
https://dl.dropboxusercontent.com/u/14381275/Sildur_1.07_0.94_Test_Intel_HD5500_10.18.14.4206_Crash.txt <- 4206, compiling errors
https://dl.dropboxusercontent.com/u/14381275/Sildur_1.07_0.94_Test_Intel_HD5500_10.18.14.4222_Crash.txt <- 4222, compiling errors

Shaders Files causing the crash/error during compiling can be found here:
http://www13.zippyshare.com/v/7Ddy1Wmq/file.html

Most of the time its the following code that causes the errors:

const ivec4 ToD[25] = ivec4[25](ivec4(0,200,134,48), //hour,r,g,b
                                ivec4(1,200,134,48),
                                ivec4(2,200,134,48),
                                ivec4(3,200,134,48),
                                ivec4(4,200,134,48),
                                ivec4(5,200,134,48),
                                ivec4(6,200,134,90),
                                ivec4(7,200,180,110),
                                ivec4(8,200,186,132),
                                ivec4(9,200,195,143),
                                ivec4(10,200,199,154),
                                ivec4(11,200,200,165),
                                ivec4(12,200,200,171),
                                ivec4(13,200,200,165),
                                ivec4(14,200,199,154),
                                ivec4(15,200,195,143),
                                ivec4(16,200,186,132),
                                ivec4(17,200,180,110),
                                ivec4(18,200,153,90),
                                ivec4(19,200,134,48),
                                ivec4(20,200,134,48),
                                ivec4(21,200,134,48),
                                ivec4(22,200,134,48),
                                ivec4(23,200,134,48),
                                ivec4(24,200,134,48));

    ivec4 temp = ToD[int(mod(floor(hour),24))];
    ivec4 temp2 = ToD[int(mod(floor(hour) + 1,24))];

[Michael_C_Intel2]

Hi Michael,

I am talking with our OpenGL driver development team about this issue. The driver teams are very busy right now so it will take some time to get this properly debugged.

-Michael

[Michael_B_14]

Michael Coppock (Intel) wrote:

Hi Michael,

I am talking with our OpenGL driver development team about this issue. The driver teams are very busy right now so it will take some time to get this properly debugged.

-Michael

Alright, thanks for the fast reply!

[Michael_C_Intel2]

Hi Michael,

We found the problem causing your issue and has fixed it in out driver. The next HSW/BDW graphics driver release will have the fix. 

-Michael

[Michael_B_14]

Michael Coppock (Intel) wrote:

Hi Michael,

We found the problem causing your issue and has fixed it in out driver. The next HSW/BDW graphics driver release will have the fix. 

-Michael

Awesome to hear! Thanks for looking at this issue!