[ANGLE] Use of uninitialized memory in ArrayBoundsClamper
authormvujovic@adobe.com <mvujovic@adobe.com@268f45cc-cd09-0410-ab3c-d52691b4dbfc>
Tue, 18 Dec 2012 19:47:22 +0000 (19:47 +0000)
committermvujovic@adobe.com <mvujovic@adobe.com@268f45cc-cd09-0410-ab3c-d52691b4dbfc>
Tue, 18 Dec 2012 19:47:22 +0000 (19:47 +0000)
commit738fce83a69f3295d56eadf7edae48440b031563
tree039c30f9c4a01f6ca25e93e4602666a9368939af
parent9aec4cd0f337644491d7c29cc04d0c15bb7ff1fb
[ANGLE] Use of uninitialized memory in ArrayBoundsClamper
https://bugs.webkit.org/show_bug.cgi?id=105218

Reviewed by Dean Jackson.

TIntermBinary::addIndexClamp is uninitialized when the compile flag
SH_CLAMP_INDIRECT_ARRAY_BOUNDS is not set. Then, addIndexClamp is used in OutputGLSLBase.
CSS Shaders needs to do a first validation pass without the SH_CLAMP_INDIRECT_ARRAY_BOUNDS
flag and its effects. However, sometimes addIndexClamp is true, which inserts clamping code
that causes a shader to fail compilation at the WebGL level.

* src/compiler/intermediate.h:
(TIntermBinary::TIntermBinary):

git-svn-id: https://svn.webkit.org/repository/webkit/trunk@138048 268f45cc-cd09-0410-ab3c-d52691b4dbfc
Source/ThirdParty/ANGLE/ChangeLog
Source/ThirdParty/ANGLE/src/compiler/intermediate.h