<feed xmlns='http://www.w3.org/2005/Atom'>
<title>go, branch go1.13.6</title>
<subtitle>Fork of Go programming language with my patches.</subtitle>
<id>http://git.kilabit.info/go/atom?h=go1.13.6</id>
<link rel='self' href='http://git.kilabit.info/go/atom?h=go1.13.6'/>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/go/'/>
<updated>2020-01-09T19:00:05Z</updated>
<entry>
<title>[release-branch.go1.13] go1.13.6</title>
<updated>2020-01-09T19:00:05Z</updated>
<author>
<name>Carlos Amedee</name>
<email>carlos@golang.org</email>
</author>
<published>2020-01-09T16:21:04Z</published>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/go/commit/?id=14b79df428fdab83ebc813a72ab714d1e2c488d2'/>
<id>urn:sha1:14b79df428fdab83ebc813a72ab714d1e2c488d2</id>
<content type='text'>
Change-Id: I8c0396849725345a12d4ca754f926714561fcc6e
Reviewed-on: https://go-review.googlesource.com/c/go/+/214080
Run-TryBot: Carlos Amedee &lt;carlos@golang.org&gt;
TryBot-Result: Gobot Gobot &lt;gobot@golang.org&gt;
Reviewed-by: Alexander Rakoczy &lt;alex@golang.org&gt;
</content>
</entry>
<entry>
<title>[release-branch.go1.13] runtime: ensure memmove write pointer atomically on ARM64</title>
<updated>2020-01-08T22:22:13Z</updated>
<author>
<name>Cherry Zhang</name>
<email>cherryyz@google.com</email>
</author>
<published>2019-12-27T17:02:00Z</published>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/go/commit/?id=acc723af2646200d13f76ffde80b000c4095074a'/>
<id>urn:sha1:acc723af2646200d13f76ffde80b000c4095074a</id>
<content type='text'>
If a pointer write is not atomic, if the GC is running
concurrently, it may observe a partially updated pointer, which
may point to unallocated or already dead memory. Most pointer
writes, like the store instructions generated by the compiler,
are already atomic. But we still need to be careful in places
like memmove. In memmove, we don't know which bits are pointers
(or too expensive to query), so we ensure that all aligned
pointer-sized units are written atomically.

Fixes #36361.
Updates #36101.

Change-Id: I1b3ca24c6b1ac8a8aaf9ee470115e9a89ec1b00b
Reviewed-on: https://go-review.googlesource.com/c/go/+/212626
Reviewed-by: Austin Clements &lt;austin@google.com&gt;
(cherry picked from commit ffbc02761abb47106ce88e09290a31513b5f6c8a)
Reviewed-on: https://go-review.googlesource.com/c/go/+/213683
Run-TryBot: Cherry Zhang &lt;cherryyz@google.com&gt;
TryBot-Result: Gobot Gobot &lt;gobot@golang.org&gt;
</content>
</entry>
<entry>
<title>[release-branch.go1.13] net/http: avoid writing to Transport.ProxyConnectHeader</title>
<updated>2020-01-07T20:29:45Z</updated>
<author>
<name>Bryan C. Mills</name>
<email>bcmills@google.com</email>
</author>
<published>2020-01-07T17:03:28Z</published>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/go/commit/?id=367da16e91af75888e44b02932d228af7c9b0244'/>
<id>urn:sha1:367da16e91af75888e44b02932d228af7c9b0244</id>
<content type='text'>
Previously, we accidentally wrote the Proxy-Authorization header for
the initial CONNECT request to the shared ProxyConnectHeader map when
it was non-nil.

Updates #36431
Fixes #36434

Change-Id: I5cb414f391dddf8c23d85427eb6973f14c949025
Reviewed-on: https://go-review.googlesource.com/c/go/+/213638
Run-TryBot: Bryan C. Mills &lt;bcmills@google.com&gt;
Reviewed-by: Brad Fitzpatrick &lt;bradfitz@golang.org&gt;
TryBot-Result: Gobot Gobot &lt;gobot@golang.org&gt;
(cherry picked from commit 249c85d3aab2ad2d0bcbf36efe606fdd66f25c72)
Reviewed-on: https://go-review.googlesource.com/c/go/+/213657
</content>
</entry>
<entry>
<title>[release-branch.go1.13] runtime: do not use PowerRegisterSuspendResumeNotification on systems with "program time" timer</title>
<updated>2020-01-03T23:38:58Z</updated>
<author>
<name>Jason A. Donenfeld</name>
<email>Jason@zx2c4.com</email>
</author>
<published>2019-11-21T15:16:56Z</published>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/go/commit/?id=b570a4147dae9efd28b48cec5b0500f599a2a99e'/>
<id>urn:sha1:b570a4147dae9efd28b48cec5b0500f599a2a99e</id>
<content type='text'>
Systems where PowerRegisterSuspendResumeNotification returns ERROR_
FILE_NOT_FOUND are also systems where nanotime() is on "program time"
rather than "real time".  The chain for this is:

powrprof.dll!PowerRegisterSuspendResumeNotification -&gt;
  umpdc.dll!PdcPortOpen -&gt;
    ntdll.dll!ZwAlpcConnectPort("\\PdcPort") -&gt;
      syscall -&gt; ntoskrnl.exe!AlpcpConnectPort

Opening \\.\PdcPort fails with STATUS_OBJECT_NAME_NOT_FOUND when pdc.sys
hasn't been initialized. Pdc.sys also provides the various hooks for
sleep resumption events, which means if it's not loaded, then our "real
time" timer is actually on "program time". Finally STATUS_OBJECT_NAME_
NOT_FOUND is passed through RtlNtStatusToDosError, which returns ERROR_
FILE_NOT_FOUND. Therefore, in the case where the function returns ERROR_
FILE_NOT_FOUND, we don't mind, since the timer we're using will
correspond fine with the lack of sleep resumption notifications. This
applies, for example, to Docker users.

Updates #35447
Updates #35482
Fixes #35746

Change-Id: I9e1ce5bbc54b9da55ff7a3918b5da28112647eee
Reviewed-on: https://go-review.googlesource.com/c/go/+/211280
Run-TryBot: Jason A. Donenfeld &lt;Jason@zx2c4.com&gt;
TryBot-Result: Gobot Gobot &lt;gobot@golang.org&gt;
Reviewed-by: Austin Clements &lt;austin@google.com&gt;
Reviewed-by: Jason A. Donenfeld &lt;Jason@zx2c4.com&gt;
</content>
</entry>
<entry>
<title>[release-branch.go1.13] runtime: call goready in wakeScavenger instead of ready</title>
<updated>2019-12-19T20:24:04Z</updated>
<author>
<name>Michael Anthony Knyszek</name>
<email>mknyszek@google.com</email>
</author>
<published>2019-10-14T17:33:36Z</published>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/go/commit/?id=b0a2a817571c52341603d7d089c4138b048c67c3'/>
<id>urn:sha1:b0a2a817571c52341603d7d089c4138b048c67c3</id>
<content type='text'>
This changes fixes an oversight in wakeScavenger which would cause ready
to be called off of the system stack. This change makes it so that
wakeScavenger calls goready, which switches to the system stack before
calling ready.

Fixes #36127.

Change-Id: Icb13f180b4d8fdd47c921eac1b896e3dd49e43b3
Reviewed-on: https://go-review.googlesource.com/c/go/+/200999
Run-TryBot: Michael Knyszek &lt;mknyszek@google.com&gt;
Reviewed-by: Keith Randall &lt;khr@golang.org&gt;
(cherry picked from commit 2c87be436bddd9b49f11959adee1ae817cb48ee1)
Reviewed-on: https://go-review.googlesource.com/c/go/+/212103
TryBot-Result: Gobot Gobot &lt;gobot@golang.org&gt;
Reviewed-by: Austin Clements &lt;austin@google.com&gt;
</content>
</entry>
<entry>
<title>[release-branch.go1.13] cmd/go/internal/modfetch: remove non-hermetic test</title>
<updated>2019-12-11T18:47:41Z</updated>
<author>
<name>Bryan C. Mills</name>
<email>bcmills@google.com</email>
</author>
<published>2019-11-05T16:01:10Z</published>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/go/commit/?id=e1df20edbb27c6fb273f530f1b4c6911c3b2e919'/>
<id>urn:sha1:e1df20edbb27c6fb273f530f1b4c6911c3b2e919</id>
<content type='text'>
The test for gopkg.in/yaml.v2@v2 assumes that there are
no future upstream releases. That assumption empirically
does not hold. Backporting fixes to this test is annoying,
and other gopkg.in cases are already reasonably covered,
so remove the problematic test.

Updates #28856

Change-Id: I6455baa1816ac69e02d1ad5d03b82a93e1481a17
Reviewed-on: https://go-review.googlesource.com/c/go/+/205437
Run-TryBot: Bryan C. Mills &lt;bcmills@google.com&gt;
Reviewed-by: Brad Fitzpatrick &lt;bradfitz@golang.org&gt;
(cherry picked from commit f0390ffc9d461cb84207b5a94c4b645c87673406)
Reviewed-on: https://go-review.googlesource.com/c/go/+/205438
Reviewed-by: Alexander Rakoczy &lt;alex@golang.org&gt;
TryBot-Result: Gobot Gobot &lt;gobot@golang.org&gt;
</content>
</entry>
<entry>
<title>[release-branch.go1.13] doc: add CherryPickApproved filter to Release History links</title>
<updated>2019-12-09T19:53:51Z</updated>
<author>
<name>Dmitri Shuralyov</name>
<email>dmitshur@golang.org</email>
</author>
<published>2019-12-05T14:13:21Z</published>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/go/commit/?id=6bf4b230234171f1cc4edab8e3eb2a989a02ddee'/>
<id>urn:sha1:6bf4b230234171f1cc4edab8e3eb2a989a02ddee</id>
<content type='text'>
Not all closed issues in a given minor milestone are included in that
release, only the ones that have been labeled as CherryPickApproved are.

Update the links to the GitHub issue tracker to include a filter on the
CherryPickApproved label, so that the default view shows only the
backports that were included in a given release. This should more useful
to most people than seeing all backports (considered and approved).

Do this only for Go 1.9.1 and newer releases, as that is when we started
using the CherryPickCandidate and CherryPickApproved labels.

Updates #35988
Fixes #36003

Change-Id: I51e07c1bc3ab9c4a5744e8f668c5470adf78bffe
Reviewed-on: https://go-review.googlesource.com/c/go/+/210117
Run-TryBot: Dmitri Shuralyov &lt;dmitshur@golang.org&gt;
Reviewed-by: Alexander Rakoczy &lt;alex@golang.org&gt;
TryBot-Result: Gobot Gobot &lt;gobot@golang.org&gt;
</content>
</entry>
<entry>
<title>[release-branch.go1.13] go1.13.5</title>
<updated>2019-12-04T21:55:02Z</updated>
<author>
<name>Carlos Amedee</name>
<email>carlos@golang.org</email>
</author>
<published>2019-12-04T20:09:21Z</published>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/go/commit/?id=9341fe073e6f7742c9d61982084874560dac2014'/>
<id>urn:sha1:9341fe073e6f7742c9d61982084874560dac2014</id>
<content type='text'>
Change-Id: I700055da44126e2dfa56f371f9e208f4f727bbed
Reviewed-on: https://go-review.googlesource.com/c/go/+/209898
Run-TryBot: Carlos Amedee &lt;carlos@golang.org&gt;
Run-TryBot: Alexander Rakoczy &lt;alex@golang.org&gt;
Reviewed-by: Alexander Rakoczy &lt;alex@golang.org&gt;
TryBot-Result: Gobot Gobot &lt;gobot@golang.org&gt;
</content>
</entry>
<entry>
<title>[release-branch.go1.13] doc: fix typo in Go 1.12.14 document</title>
<updated>2019-12-04T20:08:08Z</updated>
<author>
<name>Carlos Amedee</name>
<email>carlos@golang.org</email>
</author>
<published>2019-12-04T19:14:10Z</published>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/go/commit/?id=a1c661ad904063661219358fe6f5a740f98c4532'/>
<id>urn:sha1:a1c661ad904063661219358fe6f5a740f98c4532</id>
<content type='text'>
Change-Id: I3641a086f167a1337aaaacd2d758b6a42b84a7fb
Reviewed-on: https://go-review.googlesource.com/c/go/+/209845
Run-TryBot: Carlos Amedee &lt;carlos@golang.org&gt;
Run-TryBot: Alexander Rakoczy &lt;alex@golang.org&gt;
Reviewed-by: Alexander Rakoczy &lt;alex@golang.org&gt;
TryBot-Result: Gobot Gobot &lt;gobot@golang.org&gt;
(cherry picked from commit 98e7270a3d03c2741fc790ea619e5754c49e05ed)
Reviewed-on: https://go-review.googlesource.com/c/go/+/209877
</content>
</entry>
<entry>
<title>[release-branch.go1.13] doc: document Go 1.13.5</title>
<updated>2019-12-04T20:07:53Z</updated>
<author>
<name>Carlos Amedee</name>
<email>carlos@golang.org</email>
</author>
<published>2019-12-04T18:15:08Z</published>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/go/commit/?id=f94248fd970fa61e544a0f6baace83e2e0f6dade'/>
<id>urn:sha1:f94248fd970fa61e544a0f6baace83e2e0f6dade</id>
<content type='text'>
Change-Id: I289d13ff0a01466d93ebc555eaa81273d4297eb4
Reviewed-on: https://go-review.googlesource.com/c/go/+/209841
Run-TryBot: Carlos Amedee &lt;carlos@golang.org&gt;
Reviewed-by: Alberto Donizetti &lt;alb.donizetti@gmail.com&gt;
Reviewed-by: Alexander Rakoczy &lt;alex@golang.org&gt;
TryBot-Result: Gobot Gobot &lt;gobot@golang.org&gt;
(cherry picked from commit ebfe0574898c07e0a09a52390df1b282e2b176f7)
Reviewed-on: https://go-review.googlesource.com/c/go/+/209843
Run-TryBot: Alexander Rakoczy &lt;alex@golang.org&gt;
</content>
</entry>
</feed>
