NaCl docs: add sanitizers to GSoC ideas

native_client_sdk/doc_generated/reference/ideas.html

 {{+bindTo:partials.standard_nacl_article}}
 
 <section id="contributor-ideas">
 <span id="ideas"></span><h1 id="contributor-ideas"><span id="ideas"></span>Contributor Ideas</h1>
 <div class="contents local" id="contents" style="display: none">
 <ul class="small-gap">
 <li><a class="reference internal" href="#contributing-me" id="id9">Contributing? Me‽</a></li>
 <li><a class="reference internal" href="#google-summer-of-code" id="id10">Google Summer of Code</a></li>
 <li><p class="first"><a class="reference internal" href="#id2" id="id11">Ideas</a></p>
 <ul class="small-gap">
@@ skipping 15 matching lines @@
 </ul>
 </li>
 <li><a class="reference internal" href="#tcc" id="id23">TCC</a></li>
 <li><p class="first"><a class="reference internal" href="#llvm-and-pnacl" id="id24">LLVM and PNaCl</a></p>
 <ul class="small-gap">
 <li><a class="reference internal" href="#sandboxing-optimizations" id="id25">Sandboxing Optimizations</a></li>
 <li><a class="reference internal" href="#binary-size-reduction" id="id26">Binary Size Reduction</a></li>
 <li><a class="reference internal" href="#vector-support" id="id27">Vector Support</a></li>
 <li><a class="reference internal" href="#atomics" id="id28">Atomics</a></li>
 <li><a class="reference internal" href="#security-enhanced-pnacl" id="id29">Security-enhanced PNaCl</a></li>
+<li><a class="reference internal" href="#sanitizer-support" id="id30">Sanitizer Support</a></li>
 </ul>
 </li>
-<li><p class="first"><a class="reference internal" href="#nacl" id="id30">NaCl</a></p>
+<li><p class="first"><a class="reference internal" href="#nacl" id="id31">NaCl</a></p>
 <ul class="small-gap">
-<li><a class="reference internal" href="#auto-sandboxing" id="id31">Auto-Sandboxing</a></li>
-<li><a class="reference internal" href="#new-sandbox" id="id32">New Sandbox</a></li>
-<li><a class="reference internal" href="#bit-sandbox" id="id33">64-bit Sandbox</a></li>
+<li><a class="reference internal" href="#auto-sandboxing" id="id32">Auto-Sandboxing</a></li>
+<li><a class="reference internal" href="#new-sandbox" id="id33">New Sandbox</a></li>
+<li><a class="reference internal" href="#bit-sandbox" id="id34">64-bit Sandbox</a></li>
 </ul>
 </li>
 </ul>
 </li>
 </ul>
 
 </div><h2 id="contributing-me">Contributing? Me‽</h2>
 <p>NaCl and PNaCl are very big projects: they expose an entire operating system to
 developers, interact with all of the Web platform, and deal with compilers
 extensively to allow code written in essentially any programming language to
@@ skipping 227 matching lines @@
 system it&#8217;s running on and makes the platform even faster while keeping users
 safe. It’s also useful for non-browser uses of PNaCl such as running untrusted
 code in the Cloud. A few areas to explore are: code randomization for LLVM and
 Subzero, fuzzing of the translator, code hiding at compilation time, and code
 tuning to the hardware and operating system the untrusted code is running on.</li>
 <li><strong>Expected results:</strong> The security design and implementation successfully pass
 a review with the Chrome security team.</li>
 <li><strong>Knowledge Prerequisite:</strong> Security.</li>
 <li><strong>Mentor:</strong> JF Bastien.</li>
 </ul>
+<h4 id="sanitizer-support">Sanitizer Support</h4>
+<ul class="small-gap">
+<li><strong>Project:</strong> Sanitizer support for untrusted code.</li>
+<li><strong>Brief explanation:</strong> LLVM supports many <a class="reference external" href="http://clang.llvm.org/docs/UsersManual.html#controlling-code-generation">sanitizers</a> for C/C++ using the
+<code>-fsanitize=&lt;name&gt;</code>. Some of these sanitizers currently work, and some don&#8217;t
+because they use clever tricks to perform their work, such as using <code>mmap</code>
+to allocate a special shadow memory region with a specific address. This
+project requires adding full support to all of LLVM&#8217;s sanitizers for untrusted
+user code within PNaCl.</li>
+<li><strong>Expected results:</strong> The sanitizer tests successfully run as untrusted code
+within PNaCl.</li>
+<li><strong>Knowledge Prerequisite:</strong> Compilers.</li>
+<li><strong>Mentor:</strong> JF Bastien.</li>
+</ul>
 <h3 id="nacl">NaCl</h3>
 <h4 id="auto-sandboxing">Auto-Sandboxing</h4>
 <ul class="small-gap">
 <li><strong>Project:</strong> Auto-sandboxing assembler.</li>
 <li><strong>Brief explanation:</strong> NaCl has a toolchain which can sandbox native
 code. This toolchain can consume C/C++ as well as pre-sandboxed assembly, or
 assembly which uses special sandboxing macros. The goal of this project is to
 follow NaCl&#8217;s sandboxing requirements automatically which compiling assembly
 files.</li>
 <li><strong>Expected results:</strong> Existing assembly code can be compiled to a native
@@ skipping 26 matching lines @@
 and updating the code generation for each platform.</li>
 <li><strong>Expected results:</strong> The new sandbox&#8217;s design and implementation successfully
 pass a review with the Chrome security team. Existing NaCl code successfully
 runs in the new sandbox.</li>
 <li><strong>Knowledge Prerequisite:</strong> Security, low-level assembly, compilers, LLVM.</li>
 <li><strong>Mentor:</strong> David Sehr.</li>
 </ul>
 </section>
 
 {{/partials.standard_nacl_article}}