<feed xmlns='http://www.w3.org/2005/Atom'>
<title>go, branch go1.9beta2</title>
<subtitle>Fork of Go programming language with my patches.</subtitle>
<id>http://git.kilabit.info/go/atom?h=go1.9beta2</id>
<link rel='self' href='http://git.kilabit.info/go/atom?h=go1.9beta2'/>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/go/'/>
<updated>2017-06-26T21:12:22Z</updated>
<entry>
<title>cmd/go: add more info in t.Fatal message</title>
<updated>2017-06-26T21:12:22Z</updated>
<author>
<name>Brad Fitzpatrick</name>
<email>bradfitz@golang.org</email>
</author>
<published>2017-06-26T21:08:05Z</published>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/go/commit/?id=eab99a8d548f8ba864647ab171a44f0a5376a6b3'/>
<id>urn:sha1:eab99a8d548f8ba864647ab171a44f0a5376a6b3</id>
<content type='text'>
Updates #20284

Change-Id: I4d55d6adec4e8efb54285ca27bb4fa39c76582c3
Reviewed-on: https://go-review.googlesource.com/46719
Reviewed-by: Chris Broadfoot &lt;cbro@golang.org&gt;
</content>
</entry>
<entry>
<title>net/http/httputil: always deep copy the Request.Header map in ReverseProxy</title>
<updated>2017-06-26T19:32:47Z</updated>
<author>
<name>Brad Fitzpatrick</name>
<email>bradfitz@golang.org</email>
</author>
<published>2017-06-26T19:07:24Z</published>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/go/commit/?id=3c0f69a52101c69b5a8288195fa74c7ecfa2fa43'/>
<id>urn:sha1:3c0f69a52101c69b5a8288195fa74c7ecfa2fa43</id>
<content type='text'>
We used to do it sometimes as an optimization, but the optimization is
flawed: in all non-contrived cases we need to deep clone the map
anyway. So do it always, which both simplifies the code but also fixes
the X-Forward-For value leaking to the caller's Request, as well as
modifications from the optional Director func.

Fixes #18327

Change-Id: I0c86d10c557254bf99fdd988227dcb15f968770b
Reviewed-on: https://go-review.googlesource.com/46716
Reviewed-by: Ian Lance Taylor &lt;iant@golang.org&gt;
</content>
</entry>
<entry>
<title>runtime: drain local runq when dedicated mark worker runs</title>
<updated>2017-06-26T19:25:26Z</updated>
<author>
<name>Austin Clements</name>
<email>austin@google.com</email>
</author>
<published>2017-06-23T21:54:39Z</published>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/go/commit/?id=489620d8787a988aea4a083803608b55703f78a6'/>
<id>urn:sha1:489620d8787a988aea4a083803608b55703f78a6</id>
<content type='text'>
When the dedicated mark worker runs, the scheduler won't run on that P
again until GC runs out of mark work. As a result, any goroutines in
that P's local run queue are stranded until another P steals them. In
a normally operating system this may take a long time, and in a 100%
busy system, the scheduler never attempts to steal from another P.

Fix this by draining the local run queue into the global run queue if
the dedicated mark worker has run for long enough. We don't do this
immediately upon scheduling the dedicated mark worker in order to
avoid destroying locality if the mark worker runs for a short time.
Instead, the scheduler delays draining the run queue until the mark
worker gets its first preemption request (and otherwise ignores the
preemption request).

Fixes #20011.

Change-Id: I13067194b2f062b8bdef25cb75e4143b7fb6bb73
Reviewed-on: https://go-review.googlesource.com/46610
Run-TryBot: Austin Clements &lt;austin@google.com&gt;
TryBot-Result: Gobot Gobot &lt;gobot@golang.org&gt;
Reviewed-by: Rick Hudson &lt;rlh@golang.org&gt;
</content>
</entry>
<entry>
<title>cmd/compile: use correct variable when setting up dummy CallStmt in error</title>
<updated>2017-06-26T18:39:37Z</updated>
<author>
<name>Robert Griesemer</name>
<email>gri@golang.org</email>
</author>
<published>2017-06-26T18:12:43Z</published>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/go/commit/?id=6d594342c6fbbdc3673748b00bb8f2faaf63a0a4'/>
<id>urn:sha1:6d594342c6fbbdc3673748b00bb8f2faaf63a0a4</id>
<content type='text'>
Fixes crash when printing a related error message later on.

Fixes #20789.

Change-Id: I6d2c35aafcaeda26a211fc6c8b7dfe4a095a3efe
Reviewed-on: https://go-review.googlesource.com/46713
Run-TryBot: Robert Griesemer &lt;gri@golang.org&gt;
Reviewed-by: Josh Bleecher Snyder &lt;josharian@gmail.com&gt;
Reviewed-by: Matthew Dempsky &lt;mdempsky@google.com&gt;
TryBot-Result: Gobot Gobot &lt;gobot@golang.org&gt;
</content>
</entry>
<entry>
<title>net/http/httptest: close client connections in separate goroutines</title>
<updated>2017-06-26T18:31:26Z</updated>
<author>
<name>Yasha Bubnov</name>
<email>girokompass@gmail.com</email>
</author>
<published>2016-11-28T20:16:16Z</published>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/go/commit/?id=03305a9e0c786dab67a373106a81df56dda21e25'/>
<id>urn:sha1:03305a9e0c786dab67a373106a81df56dda21e25</id>
<content type='text'>
The existing implementation sequentially closes connection in the loop
and until the previous client connections is not closed the next one
would not be processed. Instead, the algorithm modified to spawn the
function that closes single connection in a standalone goroutine, thus
making at least a try to close it.

Change-Id: Ib96b5b477f841926450d122b67f14f1a2da36ee1
Reviewed-on: https://go-review.googlesource.com/33614
Reviewed-by: Brad Fitzpatrick &lt;bradfitz@golang.org&gt;
Run-TryBot: Brad Fitzpatrick &lt;bradfitz@golang.org&gt;
TryBot-Result: Gobot Gobot &lt;gobot@golang.org&gt;
</content>
</entry>
<entry>
<title>os/signal: check MustHaveExec in TestAtomicStop</title>
<updated>2017-06-25T15:57:18Z</updated>
<author>
<name>Ian Lance Taylor</name>
<email>iant@golang.org</email>
</author>
<published>2017-06-25T03:54:47Z</published>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/go/commit/?id=b4dd1d965dfbbde6a46bddaf6f446f4426a04b2e'/>
<id>urn:sha1:b4dd1d965dfbbde6a46bddaf6f446f4426a04b2e</id>
<content type='text'>
Change-Id: I284ecfab574b3058ba66b75f8f8d2ccdb90a8a0c
Reviewed-on: https://go-review.googlesource.com/46650
Run-TryBot: Ian Lance Taylor &lt;iant@golang.org&gt;
TryBot-Result: Gobot Gobot &lt;gobot@golang.org&gt;
Reviewed-by: Elias Naur &lt;elias.naur@gmail.com&gt;
Reviewed-by: Brad Fitzpatrick &lt;bradfitz@golang.org&gt;
</content>
</entry>
<entry>
<title>os/signal: avoid race between Stop and receiving on channel</title>
<updated>2017-06-24T00:54:01Z</updated>
<author>
<name>Ian Lance Taylor</name>
<email>iant@golang.org</email>
</author>
<published>2017-06-16T16:29:44Z</published>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/go/commit/?id=8ec7a39fec2acab98ce5e41363dd1c65c03d7479'/>
<id>urn:sha1:8ec7a39fec2acab98ce5e41363dd1c65c03d7479</id>
<content type='text'>
When Stop is called on a channel, wait until all signals have been
delivered to the channel before returning.

Use atomic operations in sigqueue to communicate more reliably between
the os/signal goroutine and the signal handler.

Fixes #14571

Change-Id: I6c5a9eea1cff85e37a34dffe96f4bb2699e12c6e
Reviewed-on: https://go-review.googlesource.com/46003
Run-TryBot: Ian Lance Taylor &lt;iant@golang.org&gt;
TryBot-Result: Gobot Gobot &lt;gobot@golang.org&gt;
Reviewed-by: Austin Clements &lt;austin@google.com&gt;
</content>
</entry>
<entry>
<title>cmd/internal/obj/arm: fix wrong encoding of MULBB</title>
<updated>2017-06-23T18:08:20Z</updated>
<author>
<name>Ben Shi</name>
<email>powerman1st@163.com</email>
</author>
<published>2017-06-23T08:05:37Z</published>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/go/commit/?id=3785457c765018a8ca5a399da177ddc5573db68d'/>
<id>urn:sha1:3785457c765018a8ca5a399da177ddc5573db68d</id>
<content type='text'>
"MULBB R1, R2, R3" is encoded to 0xe163f182, which should be
0xe1630182.

This patch fix it.

fix #20764

Change-Id: I9d3c3ffa40ecde86638e5e083eacc67578caebf4
Reviewed-on: https://go-review.googlesource.com/46491
Run-TryBot: Cherry Zhang &lt;cherryyz@google.com&gt;
TryBot-Result: Gobot Gobot &lt;gobot@golang.org&gt;
Reviewed-by: Cherry Zhang &lt;cherryyz@google.com&gt;
</content>
</entry>
<entry>
<title>os: align siginfo argument to waitid</title>
<updated>2017-06-23T17:02:41Z</updated>
<author>
<name>Ian Lance Taylor</name>
<email>iant@golang.org</email>
</author>
<published>2017-06-23T14:08:56Z</published>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/go/commit/?id=ddeab538263307f6d76e3a8a7f2c4b12383b61bc'/>
<id>urn:sha1:ddeab538263307f6d76e3a8a7f2c4b12383b61bc</id>
<content type='text'>
I have no test case for this, but there is one report on the mailing list
(https://groups.google.com/d/msg/golang-dev/sDg-t1_DPw0/-AJmLxgPBQAJ)
in which waitid running on MIPS returns EFAULT.

Change-Id: I79bde63c7427eefc1f2925d78d97cc9cf2fffde3
Reviewed-on: https://go-review.googlesource.com/46511
Run-TryBot: Ian Lance Taylor &lt;iant@golang.org&gt;
TryBot-Result: Gobot Gobot &lt;gobot@golang.org&gt;
Reviewed-by: Brad Fitzpatrick &lt;bradfitz@golang.org&gt;
</content>
</entry>
<entry>
<title>cmd/go: fix TestExecutableGOROOT when GOROOT_FINAL is set</title>
<updated>2017-06-23T15:35:55Z</updated>
<author>
<name>Russ Cox</name>
<email>rsc@golang.org</email>
</author>
<published>2017-06-23T00:08:00Z</published>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/go/commit/?id=c23948a2b83bfbe21d2d721f38a7f18f737ba7bb'/>
<id>urn:sha1:c23948a2b83bfbe21d2d721f38a7f18f737ba7bb</id>
<content type='text'>
If GOROOT_FINAL was set during the build, the default GOROOT
will not be testGOROOT. Determine the default GOROOT by reading
the right source file instead of guessing. (GOROOT_FINAL may no
longer be set when the test is actually run.)

Also refactor a bit.

Fixes #20284.

Change-Id: I2274595a235bee10c3f3a5ffecf4bb976f4d9982
Reviewed-on: https://go-review.googlesource.com/46428
Run-TryBot: Russ Cox &lt;rsc@golang.org&gt;
Reviewed-by: Ian Lance Taylor &lt;iant@golang.org&gt;
</content>
</entry>
</feed>
