Updating chromium_revision 169394:176094

This resolves ninja error on Windows due to recent depot_tools update, since a newer GYP will be synced.

Initially we ran into a compile issue with libvpx: http://code.google.com/p/webm/issues/detail?id=521
The change in libvpx.gyp is needed since the newer version of Clang that
is used with this Chromium revision provides the -fsanitize=address flag
instead of the old (now deprecated) -faddress-sanitizer. Without
disabling them when asan=1, we'll get compile errors for the assembly
offsets generated for Libvpx. See http://crbug.com/159580 for more details.

BUG=libyuv:173
TEST=trybots passing.

Review URL: https://webrtc-codereview.appspot.com/1026004

git-svn-id: http://webrtc.googlecode.com/svn/trunk@3361 4adac7df-926f-26a2-2b94-8c16560cd09d

DEPS

@@ -10,7 +10,7 @@ vars = {
   # If you do not know, use the full path while defining your new deps entry.
   "googlecode_url": "http://%s.googlecode.com/svn",
   "chromium_trunk" : "http://src.chromium.org/svn/trunk",
-  "chromium_revision": "169394",
+  "chromium_revision": "176094",
 
   # External resources like video and audio files used for testing purposes.
   # Downloaded on demand when needed.

third_party/libvpx/libvpx.gyp

@@ -347,11 +347,11 @@
       ],
       'conditions': [
         ['asan==1', {
-          'cflags!': [ '-faddress-sanitizer', ],
+          'cflags!': [ '-fsanitize=address', ],
           'xcode_settings': {
-            'OTHER_CFLAGS!': [ '-faddress-sanitizer', ],
+            'OTHER_CFLAGS!': [ '-fsanitize=address', ],
           },
-          'ldflags!': [ '-faddress-sanitizer', ],
+          'ldflags!': [ '-fsanitize=address', ],
         }],
       ],
       'sources': [