Remove all code related to NaCl

site/dev/contrib/c++11.md

 C++11 in Skia
 =============
 
 Skia is exploring the use of C++11.  As a library, we are technically limited
 by what our clients support and what our build bots support.
 
 Skia may also be limited by restrictions we choose put on ourselves.  This
 document is not concerned with C++11 policy in Skia, only its technical
 feasibility.  This is about what we can use, a superset of what we may use.
 
@@ skipping 43 matching lines @@
 ----
 
 Most of our bots are pretty up-to-date: the Windows bots use MSVC 2013, the Mac
 bots a recent Clang, and the Linux bots GCC 4.8 or a recent Clang.  Our Android
 bots use a recent toolchain from Android (see above), and our Chrome bots use
 Chrome's toolchains (see above).  I'm not exactly sure what our Chrome OS bots
 are using, but they've never been a problem.
 
 A few miscellaneous compile-only bots are actually our current overall weak link:
 
--   Our NaCl builds use an old non-PNaCl toolchain, which is based on GCC
-    4.4.  GCC 4.4 has some support for C++11, but it's not nearly complete.
-    There is no upgrade path except PNaCl; even the very latest NaCl toolchain
-    is GCC 4.4, while PNaCl is based on Clang 3.4 (with complete C++11 support).
 -   Our iOS builds are driven from a Mac 10.7 machine using some unknown old Clang.
     Who knows how old that is or what it supports?  It's probably due for an update.
 
-If we were to eliminate the problems of the NaCl and iOS bots, our ability to
+If we were to eliminate the problems of iOS bots, our ability to
 use C++11 would match Mozilla's list nearly identically.