summaryrefslogtreecommitdiffstats
path: root/chrome/test/data
diff options
context:
space:
mode:
authorthakis@chromium.org <thakis@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2010-02-27 02:14:42 +0000
committerthakis@chromium.org <thakis@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2010-02-27 02:14:42 +0000
commit85c6d6739a81098c35cb35c3430f038ed4f5ddab (patch)
treee9302aab1b4368f28f3188087c2cb2d9521b103c /chrome/test/data
parent85aa75c358eded70e4ebe9038d5133847d335b7f (diff)
downloadchromium_src-85c6d6739a81098c35cb35c3430f038ed4f5ddab.zip
chromium_src-85c6d6739a81098c35cb35c3430f038ed4f5ddab.tar.gz
chromium_src-85c6d6739a81098c35cb35c3430f038ed4f5ddab.tar.bz2
"/b/slave/chromium-rel-linux/build/src/gpu/command_buffer/client/gles2_demo_cc.cc:50:warning: 'length' may be used uninitialized in this function"
Revert 40193 - Added support for glGetString, glGetShaderSource, glGetProgramInfoLog and glGetShaderInfoLog This turned up lots of issues. * glGetShaderiv needed to be wrapped so it returns the size of the shader the user passed in. Not the munged shader sent to GL. * Another issue that came up is that client side validation is needed to ensure that the client side GLES2Implementation does not generate bad commands. For example, calling glUniform1iv with a negative count would generate a bad command. The service side would see that and think the program was malicious and stop processing commands. So, that means I had to add some client side validation and wrap glGetError on the client side so I can synthisize GL errors there. TEST=lots of unit tests. BUG=none Review URL: http://codereview.chromium.org/661220 TBR=gman@chromium.org Review URL: http://codereview.chromium.org/660229 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@40198 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/test/data')
0 files changed, 0 insertions, 0 deletions