Fix chrome/arm build warnings.

build/common.gypi

Index: build/common.gypi
diff --git a/build/common.gypi b/build/common.gypi
index 96e2fb79a55a8ab76b508638e2dccd4228544c8e..223f7a95eb516a80245b6bdb33016a84352dd2ec 100644
--- a/build/common.gypi
+++ b/build/common.gypi
@@ -1492,6 +1492,17 @@
       # Targets are by default not nacl untrusted code.
       'nacl_untrusted_build%': 0,
 
+      'pnacl_compile_flags': [
+        # pnacl uses the clang compiler so we need to supress all the
+        # same warnings as we do for clang.

[Nico, 2012/11/13 22:53:49]

Which version of clang does pnacl use?

[Sam Clegg, 2012/11/13 23:24:46]

3.2.   I think they track upstream fairly closely.

[Nico, 2012/11/13 23:27:24]

3.2 isn't released yet. So this is different from the clang revision we use in
chromium (
http://commondatastorage.googleapis.com/chromium-browser-clang/index.html ), or
is their clang cut at the same revisions? How much of chromium's code has to be
buildable with nacl clang? What's their compiler update process?

+        # TODO(sbc): Remove these if/when they are removed from the clang
+        # build.
+        '-Wno-unused-function',
+        '-Wno-char-subscripts',
+        '-Wno-c++11-extensions',
+        '-Wno-unnamed-type-template-args',
+      ],
+
       'conditions': [
         ['OS=="win" and component=="shared_library"', {
           # See http://msdn.microsoft.com/en-us/library/aa652367.aspx