It's causing trouble with Aura. Locking the screen seems to generate the display mode change device status and Aura cannot recover.

http://crbug.com/178148
Review URL: https://codereview.appspot.com/7398052

git-svn-id: https://angleproject.googlecode.com/svn/trunk@1834 736b8ea6-26fd-11df-bfd4-992fa37f6226

Review URL: https://codereview.appspot.com/7381049

git-svn-id: https://angleproject.googlecode.com/svn/trunk@1833 736b8ea6-26fd-11df-bfd4-992fa37f6226

1) Remove an empty file: this causes patch apply failures when updating WebKit side ANGLE.
2) Fix a 64-to-32 conversion issue.
3) Append a change to Tokenizer.l that's left out in a previous CL. (cpp is already updated).
Review URL: https://codereview.appspot.com/7378051

git-svn-id: https://angleproject.googlecode.com/svn/trunk@1832 736b8ea6-26fd-11df-bfd4-992fa37f6226

Original patch: http://trac.webkit.org/changeset/139665
Review URL: https://codereview.appspot.com/7392044

git-svn-id: https://angleproject.googlecode.com/svn/trunk@1831 736b8ea6-26fd-11df-bfd4-992fa37f6226

Review URL: https://codereview.appspot.com/7308107

git-svn-id: https://angleproject.googlecode.com/svn/trunk@1830 736b8ea6-26fd-11df-bfd4-992fa37f6226

Sometimes IDirect3DDevice9Ex::CheckDeviceState returns S_PRESENT_MODE_CHANGED when the GPU has hung. It's not consistent, maybe one time out of two when I hang the GPU while running WebGL Aquarium.

This unfortunately means that changes to display mode will cause ANGLE to report context lost. Other ideas appreciated.
Review URL: https://codereview.appspot.com/7305093

git-svn-id: https://angleproject.googlecode.com/svn/trunk@1829 736b8ea6-26fd-11df-bfd4-992fa37f6226

Review URL: https://codereview.appspot.com/7330046

git-svn-id: https://angleproject.googlecode.com/svn/trunk@1828 736b8ea6-26fd-11df-bfd4-992fa37f6226

BUG=396
Review URL: https://codereview.appspot.com/7323055

git-svn-id: https://angleproject.googlecode.com/svn/trunk@1827 736b8ea6-26fd-11df-bfd4-992fa37f6226

This is an incompatible API change, but one which is necessary in
order to improve correctness of the code. The API version in
ShaderLang.h is updated and, unfortunately, the define renamed to
something less ambiguous due to conflicts on some Android buildbots.
Temporary patches in Chromium and WebKit will be landed separately to
support this upgrade.

BUG=403,404,405,406,407,408,409
Review URL: https://codereview.appspot.com/7300058

git-svn-id: https://angleproject.googlecode.com/svn/trunk@1826 736b8ea6-26fd-11df-bfd4-992fa37f6226

ProgramBinary::save writes a size_t, so ProgramBinary::load needs
to read it as the same type.

Landed for jschuh.
Original review: https://codereview.appspot.com/7304057/
Review URL: https://codereview.appspot.com/7310052

git-svn-id: https://angleproject.googlecode.com/svn/trunk@1825 736b8ea6-26fd-11df-bfd4-992fa37f6226

Fixes new WebGL conformance tests
shader-with-illegal-default-precision.frag.html and
shader-with-illegal-default-precision.vert.html per
http://www.khronos.org/bugzilla/show_bug.cgi?id=781 . Also ran WebGL
1.0.1 conformance tests; no regressions.

BUG=none
Review URL: https://codereview.appspot.com/7302043

git-svn-id: https://angleproject.googlecode.com/svn/trunk@1824 736b8ea6-26fd-11df-bfd4-992fa37f6226

git-svn-id: https://angleproject.googlecode.com/svn/trunk@1823 736b8ea6-26fd-11df-bfd4-992fa37f6226

git-svn-id: https://angleproject.googlecode.com/svn/trunk@1821 736b8ea6-26fd-11df-bfd4-992fa37f6226

TBR=alokp
Review URL: https://codereview.appspot.com/7228076

git-svn-id: https://angleproject.googlecode.com/svn/trunk@1810 736b8ea6-26fd-11df-bfd4-992fa37f6226

With this fixed, Chrome behaves the same on WebGL conformance tests 1.0.2 with/without --enable-shader-name-hashing

BUG=
TEST=WebGL conformance tests
Review URL: https://codereview.appspot.com/7229043

git-svn-id: https://angleproject.googlecode.com/svn/trunk@1809 736b8ea6-26fd-11df-bfd4-992fa37f6226

Trac #21120

git-svn-id: https://angleproject.googlecode.com/svn/trunk@1807 736b8ea6-26fd-11df-bfd4-992fa37f6226

Trac #21120

    01/30/2013  dgkoch  add issue 6 and clear interactions
                        renamed to EXT_draw_buffers based on feedback
                        changed resolution of issue 3.

git-svn-id: https://angleproject.googlecode.com/svn/trunk@1806 736b8ea6-26fd-11df-bfd4-992fa37f6226

git-svn-id: https://angleproject.googlecode.com/svn/trunk@1805 736b8ea6-26fd-11df-bfd4-992fa37f6226

Review URL: https://codereview.appspot.com/7221045

git-svn-id: https://angleproject.googlecode.com/svn/trunk@1804 736b8ea6-26fd-11df-bfd4-992fa37f6226

So len could equal = max_len, and at this point name[len] is out of the range.

BUG=
TEST=
Review URL: https://codereview.appspot.com/7223045

git-svn-id: https://angleproject.googlecode.com/svn/trunk@1803 736b8ea6-26fd-11df-bfd4-992fa37f6226

BUG=none
TEST=compiled on Linux and Mac OS
Review URL: https://codereview.appspot.com/7133076

git-svn-id: https://angleproject.googlecode.com/svn/trunk@1735 736b8ea6-26fd-11df-bfd4-992fa37f6226

this optimization level, it appears that array index clamping can be
enabled on Windows without destabilizing WebGL content.

Tested this change with array index clamping enabled with MapsGL, a
previous failing test from AlteredQualia, many Three.js demos, the
Julia Set tutorial from acko.net, the WebGL 1.0.1 conformance suite,
and other content; all worked.

BUG=none
Review URL: https://codereview.appspot.com/7197054

git-svn-id: https://angleproject.googlecode.com/svn/trunk@1734 736b8ea6-26fd-11df-bfd4-992fa37f6226

array index clamping to use the clamp intrinsic. This works more
reliably on pure OpenGL ES devices and on Windows.

Added a mechanism in ShBuiltInResources to choose the strategy for
array index clamping.

BUG=none
TEST=various out-of-bounds array indexing tests and various WebGL content
Review URL: https://codereview.appspot.com/7194051

git-svn-id: https://angleproject.googlecode.com/svn/trunk@1733 736b8ea6-26fd-11df-bfd4-992fa37f6226

BUG=none
TEST=compiled on Linux
Review URL: https://codereview.appspot.com/7201056

git-svn-id: https://angleproject.googlecode.com/svn/trunk@1732 736b8ea6-26fd-11df-bfd4-992fa37f6226

git-svn-id: https://angleproject.googlecode.com/svn/trunk@1731 736b8ea6-26fd-11df-bfd4-992fa37f6226

git-svn-id: https://angleproject.googlecode.com/svn/trunk@1730 736b8ea6-26fd-11df-bfd4-992fa37f6226

Review URL: https://codereview.appspot.com/7193053

git-svn-id: https://angleproject.googlecode.com/svn/trunk@1729 736b8ea6-26fd-11df-bfd4-992fa37f6226

Chrome now builds ANGLE against the Windows 8 Platform SDK.

Move the include and lib search paths to common.gypi so that downstream projects can specify the location of the Platform SDK or alternatively use the DirectX SDK instead.
Review URL: https://codereview.appspot.com/7193052

git-svn-id: https://angleproject.googlecode.com/svn/trunk@1728 736b8ea6-26fd-11df-bfd4-992fa37f6226

This is to fix the standalone gyp build. It couldn't handle changes made in r1721. This is the latest version.
Review URL: https://codereview.appspot.com/7204049

git-svn-id: https://angleproject.googlecode.com/svn/trunk@1727 736b8ea6-26fd-11df-bfd4-992fa37f6226

Review URL: https://codereview.appspot.com/7204048

git-svn-id: https://angleproject.googlecode.com/svn/trunk@1726 736b8ea6-26fd-11df-bfd4-992fa37f6226

These conflict with the STL functions of the same name.

This is to make the standalone ANGLE gyp build work again.
Review URL: https://codereview.appspot.com/7211043

git-svn-id: https://angleproject.googlecode.com/svn/trunk@1725 736b8ea6-26fd-11df-bfd4-992fa37f6226

This is to make the standalone gyp build work again.
Review URL: https://codereview.appspot.com/7199046

git-svn-id: https://angleproject.googlecode.com/svn/trunk@1724 736b8ea6-26fd-11df-bfd4-992fa37f6226

This is so that texture2D is converted to texture2DLod in loops with return statements. HLSL does not seem to allow gradient operations in loops with return statements. It considers them to be breaks.
Review URL: https://codereview.appspot.com/7131057

git-svn-id: https://angleproject.googlecode.com/svn/trunk@1722 736b8ea6-26fd-11df-bfd4-992fa37f6226

Addendum to https://codereview.appspot.com/7011048/

BUG=391, chromium:166496, chromium:167187

Landing for jschuh
Original patch: https://codereview.appspot.com/7075044/
Review URL: https://codereview.appspot.com/7190044

git-svn-id: https://angleproject.googlecode.com/svn/trunk@1721 736b8ea6-26fd-11df-bfd4-992fa37f6226

was not used to do the bounds clamping.

BUG=397



git-svn-id: https://angleproject.googlecode.com/svn/trunk@1720 736b8ea6-26fd-11df-bfd4-992fa37f6226

Review URL: https://codereview.appspot.com/7105049

git-svn-id: https://angleproject.googlecode.com/svn/trunk@1719 736b8ea6-26fd-11df-bfd4-992fa37f6226

Review URL: https://codereview.appspot.com/7062061

git-svn-id: https://angleproject.googlecode.com/svn/trunk@1647 736b8ea6-26fd-11df-bfd4-992fa37f6226

It looks like this now:
ANGLE (NVIDIA Quadro 600 Direct3D9Ex vs_3_0 ps_3_0)

I also noticed that the strings returned by GetString are not all static so I fixed that as well.
Review URL: https://codereview.appspot.com/7068058

git-svn-id: https://angleproject.googlecode.com/svn/trunk@1646 736b8ea6-26fd-11df-bfd4-992fa37f6226

BUG=
TEST=build fine in Linux
Review URL: https://codereview.appspot.com/7071056

git-svn-id: https://angleproject.googlecode.com/svn/trunk@1645 736b8ea6-26fd-11df-bfd4-992fa37f6226

C++ streams seem to use the representation 1.$ for INF and that isn't valid syntax in GLSL or HLSL.

Also preserve the sign of INF in constant expressions that divide by zero. I can't figure out what to do about 0/0 because the shader models we are using do not support NaN. Treating it as +INF as before.
Review URL: https://codereview.appspot.com/7057046

git-svn-id: https://angleproject.googlecode.com/svn/trunk@1644 736b8ea6-26fd-11df-bfd4-992fa37f6226