PNaCl documentation: update the bitcode reference manual for vector load/store

native_client_sdk/doc_generated/reference/pnacl-bitcode-abi.html

 {{+bindTo:partials.standard_nacl_article}}
 
 <section id="pnacl-bitcode-reference-manual">
 <h1 id="pnacl-bitcode-reference-manual">PNaCl Bitcode Reference Manual</h1>
 <div class="contents local" id="contents" style="display: none">
 <ul class="small-gap">
 <li><a class="reference internal" href="#introduction" id="id1">Introduction</a></li>
 <li><p class="first"><a class="reference internal" href="#high-level-structure" id="id2">High Level Structure</a></p>
 <ul class="small-gap">
 <li><a class="reference internal" href="#data-model" id="id3">Data Model</a></li>
@@ skipping 183 matching lines @@
 128-bits).</li>
 </ul>
 </section><section id="array-and-struct-types">
 <h3 id="array-and-struct-types">Array and struct types</h3>
 <p>Array and struct types are only allowed in
 <a class="reference internal" href="#bitcode-globalvariables"><em>global variable initializers</em></a>.</p>
 </section><section id="pointer-types">
 <span id="bitcode-pointertypes"></span><h3 id="pointer-types"><span id="bitcode-pointertypes"></span>Pointer types</h3>
 <p>Only the following pointer types are allowed:</p>
 <ul class="small-gap">
-<li>Pointers to valid PNaCl bitcode scalar types, as specified above.</li>
+<li>Pointers to valid PNaCl bitcode scalar types, as specified above, except for
+<code>i1</code>.</li>
+<li>Pointers to valid PNaCl bitcode vector types, as specified above, except for
+<code>&lt;? x i1&gt;</code>.</li>
 <li>Pointers to functions.</li>
 </ul>
 <p>In addition, the address space for all pointers must be 0.</p>
 <p>A pointer is <em>inherent</em> when it represents the return value of an <code>alloca</code>
 instruction, or is an address of a global value.</p>
 <p>A pointer is <em>normalized</em> if it&#8217;s either:</p>
 <ul class="small-gap">
 <li><em>inherent</em></li>
 <li>Is the return value of a <code>bitcast</code> instruction.</li>
 <li>Is the return value of a <code>inttoptr</code> instruction.</li>
@@ skipping 65 matching lines @@
 Unlike the libc fmod function, this does not set <code>errno</code> when the
 result is NaN (see the <a class="reference internal" href="#ir-and-errno"><em>instructions and errno</em></a>
 section).</p>
 </li>
 <li><p class="first"><code>alloca</code></p>
 <p>See <a class="reference internal" href="#bitcode-allocainst"><em>alloca instructions</em></a>.</p>
 </li>
 <li><p class="first"><code>load</code>, <code>store</code></p>
 <p>The pointer argument of these instructions must be a <em>normalized</em> pointer (see
 <a class="reference internal" href="#bitcode-pointertypes"><em>pointer types</em></a>). The <code>volatile</code> and <code>atomic</code>
-attributes are not supported. Loads and stores of the type <code>i1</code> are not
-supported.</p>
-<p>These instructions must use <code>align 1</code> on integer memory accesses, <code>align 4</code>
-for <code>float</code> accesses and <code>align 8</code> for <code>double</code> accesses.</p>
+attributes are not supported. Loads and stores of the type <code>i1</code> and <code>&lt;? x
+i1&gt;</code> are not supported.</p>
+<p>These instructions must follow the following alignment restrictions:</p>
+<ul class="small-gap">
+<li>On integer memory accesses: <code>align 1</code>.</li>
+<li>On <code>float</code> memory accesses: <code>align 1</code> or <code>align 4</code>.</li>
+<li>On <code>double</code> memory accesses: <code>align 1</code> or <code>align 8</code>.</li>
+<li>On vector memory accesses: alignment at the vector&#8217;s element width, for
+example <code>&lt;4 x i32&gt;</code> must be <code>align 4</code>.</li>
+</ul>
 </li>
 <li><code>trunc</code></li>
 <li><code>zext</code></li>
 <li><code>sext</code></li>
 <li><code>fptrunc</code></li>
 <li><code>fpext</code></li>
 <li><code>fptoui</code></li>
 <li><code>fptosi</code></li>
 <li><code>uitofp</code></li>
 <li><code>sitofp</code></li>
@@ skipping 156 matching lines @@
 <p>The <code>llvm.nacl.atomic.is.lock.free</code> intrinsic is designed to
 determine at translation time whether atomic operations of a certain
 <code>byte_size</code> (a compile-time constant), at a particular <code>address</code>,
 are lock-free or not. This reflects the C11 <code>atomic_is_lock_free</code>
 function from header <code>&lt;stdatomic.h&gt;</code> and the C++11 <code>is_lock_free</code>
 member function in header <code>&lt;atomic&gt;</code>. It can be used through the
 <code>__nacl_atomic_is_lock_free</code> builtin.</p>
 </section></section></section>
 
 {{/partials.standard_nacl_article}}