glsl "FOR" loop with texture2D gives "D3D shader compilation fail"

[GoogleCodeExporter]

What steps will reproduce the problem?
1. open 
http://kuranes.github.io/osgjs/examples/shadowmap/?debug=1&kernelSizePCF=8Poisso
n(32texFetch) with a windows chrome (nvidia dx11)
2. all glsl shader using a FOR loop for texFetching shadowmap blocker depth 
gives "D3D shader compilation fails"
3. see the shader compilation fail (in console.log)

What is the expected output? What do you see instead?
Expect a shader compilation working (and give nice if slow shadows) and I see 
instead a Shader compilation fail (when shader compilaton fails we output 
#FF00FF color)

What version of the product are you using? On what operating system?
- windows 7 64 bits
- chrome 40.0.2214.111 m (64-bit) (same on canary  42.0.2305.2 canary (64-bit))

Please provide any additional information below.
- Works on firefox on same platforms, and on other platform chrome (osx)
All of the PCF filters that use glsl "for" instead of unrolled loops fail, as 
you can check using the gui combobox. (16Band,9TAP,16TAP,all POISSON)
Note that If I unroll the loops it works.  (which I did here until bug fixed 
here 
https://github.com/cedricpinson/osgjs/commit/a75e134677bf80d1b0cb119cd24b7cb8a65
38764#diff-2355b511a15e567b0269e2ad25c93427L108  )

Original issue reported on code.google.com by tuan.kur...@gmail.com on 16 Feb 2015 at 9:32

[GoogleCodeExporter]

Nicolas, Jamie-- is this a case of hitting loop complexity/unrolling limits in 
the D3D compiler? Working in Firefox may just be indicative of a difference 
between the d3d9/d3d11 compilers.

Original comment by shannonw...@chromium.org on 17 Feb 2015 at 6:08

[GoogleCodeExporter]

Original comment by geofflang@chromium.org on 24 Feb 2015 at 9:41

• Changed state: Started

[GoogleCodeExporter]

https://chromium-review.googlesource.com/#/c/252986/

Original comment by geofflang@chromium.org on 24 Feb 2015 at 9:48

• Changed state: Fixed