Commit e71276c7 authored by Rob Pike's avatar Rob Pike

doc: add -test.count and get -insecure to go1.5.html

Change-Id: Ie3d603a95826b9b6a7acd4825991f24c3c61408b
Reviewed-on: https://go-review.googlesource.com/11956Reviewed-by: default avatarRuss Cox <rsc@golang.org>
parent 91976aa6
...@@ -355,25 +355,18 @@ manual verification may be required. ...@@ -355,25 +355,18 @@ manual verification may be required.
</p> </p>
<p> <p>
Perhaps more important is that some discrepancies between the Perhaps more important is that on machines where
architectures in how the PC and SP are handled have been <code>SP</code> or <code>PC</code> is only an alias
eliminated. for a numbered register,
Sometimes these registers represented hardware such as <code>R13</code> for the stack pointer and
registers, and sometimes pseudo-registers. <code>R15</code> for the hardware program counter
As of Go 1.5, the names <code>PC</code> and <code>SP</code> on x86,
are always pseudo-registers. a reference to such a register that does not include a symbol
To refer to the hardware register, use the alternate representation such is now illegal.
as <code>R13</code> for the stack pointer and For example, <code>SP</code> and <code>4(SP)</code> are
<code>R15</code> for the hardware program counter on x86. illegal but <code>sym+4(SP)</code> is fine.
(The names are different on other architectures.) On such machines, to refer to the hardware register use its
To help enforce this change, references to the true <code>R</code> name.
<code>SP</code> and <code>PC</code>
pseudo-registers now always require an identifier:
<code>f+4(SP)</code> not <code>4(SP)</code>;
it is a syntax error to omit the identifier.
Uses of <code>SP</code> (say) as a hardware register
tend to omit the name, and they will now be flagged by
the assembler.
</p> </p>
<p> <p>
...@@ -487,11 +480,15 @@ as described above. ...@@ -487,11 +480,15 @@ as described above.
An <code>-asmflags</code> build option has been added to provide An <code>-asmflags</code> build option has been added to provide
flags to the assembler. flags to the assembler.
However, However,
the <code>-ccflags</code> build option has been dropped. TODO: why? the <code>-ccflags</code> build option has been dropped;
it was specific to the old, now deleted C compiler .
</li> </li>
<li> <li>
cmd/go, testing: add go test -count (https://golang.org/cl/10669) The <code>test</code> subcommand now has a <code>-count</code>
flag to specify how many times to run each test and benchmark.
<a href="/pkg/testing/"><code>testing</code></a> package
does the work here, through by the <code>-test.count</code> flag.
</li> </li>
<li> <li>
...@@ -503,6 +500,12 @@ The executing pattern now has access to two new environment variables: ...@@ -503,6 +500,12 @@ The executing pattern now has access to two new environment variables:
and <code>$DOLLAR</code> expands to a dollar sign. and <code>$DOLLAR</code> expands to a dollar sign.
</li> </li>
<li>
The <code>get</code> subcommand now has a <code>-insecure</code>
flag that must be enabled if fetching from an insecure repository, one that
does not encrypt the connection.
</li>
</ul> </ul>
<h3 id="vet_command">Go vet command</h3> <h3 id="vet_command">Go vet command</h3>
...@@ -800,7 +803,7 @@ The server serves them if they are listed in the ...@@ -800,7 +803,7 @@ The server serves them if they are listed in the
<a href="/pkg/crypto/tls/#Certificate"><code>Certificate</code></a> struct, <a href="/pkg/crypto/tls/#Certificate"><code>Certificate</code></a> struct,
and the client requests them and exposes them, if present, and the client requests them and exposes them, if present,
in its <a href="/pkg/crypto/tls/#ConnectionState"><code>ConnectionState</code></a> struct. in its <a href="/pkg/crypto/tls/#ConnectionState"><code>ConnectionState</code></a> struct.
The <a href="/pkg/crytpo/tls/"><code>crytpo/tls</code></a> server implementation The <a href="/pkg/crypto/tls/"><code>crytpo/tls</code></a> server implementation
will also now always call the will also now always call the
<code>GetCertificate</code> function in <code>GetCertificate</code> function in
the <a href="/pkg/crypto/tls/#Config"><code>Config</code></a> struct the <a href="/pkg/crypto/tls/#Config"><code>Config</code></a> struct
...@@ -1039,13 +1042,6 @@ Also, starting with Go 1.5 the package sets the <code>REMOTE_PORT</code> ...@@ -1039,13 +1042,6 @@ Also, starting with Go 1.5 the package sets the <code>REMOTE_PORT</code>
variable. variable.
</li> </li>
<li>
The <a href="/pkg/net/http/"><code>net/http</code></a> package's
<a href="/pkg/net/http#Request"><code>Request</code></a> type adds a
<code>Cancel</code> field, a channel to signal that the request has been
canceled.
</li>
<li> <li>
The <a href="/pkg/net/mail/"><code>net/mail</code></a> package The <a href="/pkg/net/mail/"><code>net/mail</code></a> package
adds a <a href="/pkg/net/mail/#AddressParser"><code>AddressParser</code></a> adds a <a href="/pkg/net/mail/#AddressParser"><code>AddressParser</code></a>
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment