Integrate syzygy (optionally) into the chrome build process.

DEPS

Index: DEPS
===================================================================
--- DEPS	(revision 95033)
+++ DEPS	(working copy)
@@ -310,6 +310,11 @@
     # Dependencies used by libjpeg-turbo
     "src/third_party/yasm/binaries":
       "/trunk/deps/third_party/yasm/binaries@74228",
+
+    # Binary level profile guided optimizations.  This points to the
+    # latest release binaries for the toolchain.
+    "src/third_party/syzygy/binaries":
+      "https://sawbuck.googlecode.com/svn/trunk/syzygy/binaries",

[Roger McFarlane (Google), 2011/08/03 16:22:28]

Pull this from our repo or commit our releases directly into the chrome tree? 
i.e.:

  /trunk/deps/third_party/syzygy/binaries

[Roger McFarlane (Google), 2011/08/03 17:06:55]

nsylvain@ further suggests that everything should be pinned in thest DEPS files
(actually he was talking about the internal DEPS at the time, but I would
presume it applies here as well).

[M-A Ruel, 2011/08/03 17:32:59]

Yes please.

   },
   "mac": {
     "src/chrome/tools/test/reference_build/chrome_mac":