code review 6550058: build: make int 64 bits on amd64

doc/go_faq.html

 <!--{
-        "Title": "FAQ"
+        "Title": "FAQ",
+        "Path": "/doc/faq"
 }-->
 
 <h2 id="Origins">Origins</h2>
 
 <h3 id="What_is_the_purpose_of_the_project">
 What is the purpose of the project?</h3>
 
 <p>
 No major systems language has emerged in over a decade, but over that time
 the computing landscape has changed tremendously. There are several trends:
@@ skipping 1032 matching lines @@
 See the <a href="/doc/effective_go.html#allocation_new">relevant section
 of Effective Go</a> for more details.
 </p>
 
 <h3 id="q_int_sizes">
 Why is <code>int</code> 32 bits on 64 bit machines?</h3>
 
 <p>
 The sizes of <code>int</code> and <code>uint</code> are implementation-specific
 but the same as each other on a given platform.
-The 64 bit Go compilers (both gc and gccgo) use a 32 bit representation for
-<code>int</code>.  Code that relies on a particular
+For portability, code that relies on a particular
 size of value should use an explicitly sized type, like <code>int64</code>.
+Prior to Go 1.1, the 64-bit Go compilers (both gc and gccgo) used
+a 32-bit representation for <code>int</code>. As of Go 1.1 they use
+a 64-bit representation.
 On the other hand, floating-point scalars and complex
 numbers are always sized: <code>float32</code>, <code>complex64</code>,
 etc., because programmers should be aware of precision when using
 floating-point numbers.
 The default size of a floating-point constant is <code>float64</code>.
 </p>
 
 <p>
 At the moment, all implementations use 32-bit ints, an essentially arbitrary decision.
 However, we expect that <code>int</code> will be increased to 64 bits on 64-bit
@@ skipping 626 matching lines @@
 <p>
 On the topic of performance, keep in mind that Go gives the programmer
 considerable control over memory layout and allocation, much more than
 is typical in garbage-collected languages. A careful programmer can reduce
 the garbage collection overhead dramatically by using the language well;
 see the article about
 <a href="http://blog.golang.org/2011/06/profiling-go-programs.html">profiling
 Go programs</a> for a worked example, including a demonstration of Go's
 profiling tools.
 </p>