delta/go-git.git/src/runtime, branch dev.boringcrypto.go1.12

[dev.boringcrypto.go1.12] all: merge go1.12.17 into dev.boringcrypto.go1.12

2020-02-13T00:41:23+00:00

Change-Id: I2d0dd2e7e141bbcebd3a4ae72d1e149997af3d26

[dev.boringcrypto.go1.12] all: merge go1.12.16 into dev.boringcrypto.go1.12

2020-02-04T22:53:10+00:00

Change-Id: I4e773f39dc51294fd43d1478fce54d286f8e2805

[release-branch.go1.12] runtime: ignore power notification error seen on Windows Docker

2020-01-16T19:05:18+00:00

Updates #36557
Fixes #36574

Change-Id: Ia8125f382d5e14e5612da811268a58971cc9ac08
Reviewed-on: https://go-review.googlesource.com/c/go/+/214917
Run-TryBot: Ian Lance Taylor 
TryBot-Result: Gobot Gobot 
Reviewed-by: Brad Fitzpatrick 
Reviewed-by: Jason A. Donenfeld 
Reviewed-by: Austin Clements 
(cherry picked from commit d2de9bd59c068c1bfcb4293de4286196dacf2e43)
Reviewed-on: https://go-review.googlesource.com/c/go/+/215017

[release-branch.go1.12] runtime: ensure memmove write pointer atomically on ARM64

2020-01-08T22:22:22+00:00

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 #36367.
Updates #36101.

Change-Id: I1b3ca24c6b1ac8a8aaf9ee470115e9a89ec1b00b
Reviewed-on: https://go-review.googlesource.com/c/go/+/212626
Reviewed-by: Austin Clements 
(cherry picked from commit ffbc02761abb47106ce88e09290a31513b5f6c8a)
Reviewed-on: https://go-review.googlesource.com/c/go/+/213684
Run-TryBot: Cherry Zhang 
TryBot-Result: Gobot Gobot

[release-branch.go1.12] runtime: do not use PowerRegisterSuspendResumeNotification on systems with "program time" timer

2020-01-03T23:40:29+00:00

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 ->
  umpdc.dll!PdcPortOpen ->
    ntdll.dll!ZwAlpcConnectPort("\\PdcPort") ->
      syscall -> 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 #36377

Change-Id: I9e1ce5bbc54b9da55ff7a3918b5da28112647eee
Reviewed-on: https://go-review.googlesource.com/c/go/+/208317
Reviewed-by: Jason A. Donenfeld 
Reviewed-by: Austin Clements 
Run-TryBot: Jason A. Donenfeld 
TryBot-Result: Gobot Gobot 
Reviewed-on: https://go-review.googlesource.com/c/go/+/213198

[release-branch.go1.12] runtime: monitor for suspend/resume to kick timeouts

2020-01-03T23:37:47+00:00

Starting in Windows 8, the wait functions don't take into account
suspend time, even though the monotonic counters do. This results in
timer buckets stalling on resume. Therefore, this commit makes it so
that on resume, we return from the wait functions and recalculate the
amount of time left to wait.

This is a cherry pick of CL 191957 and its cleanup, CL 198417.

Updates #31528
Fixes #36376

Change-Id: I0db02cc72188cb620954e87a0180e0a3c83f4a56
Reviewed-on: https://go-review.googlesource.com/c/go/+/193607
Run-TryBot: Jason A. Donenfeld 
TryBot-Result: Gobot Gobot 
Reviewed-by: Austin Clements 
Reviewed-on: https://go-review.googlesource.com/c/go/+/213197

[release-branch.go1.12] runtime: fix textOff for multiple text sections

2019-12-04T17:11:12+00:00

If a compilation has multiple text sections, code in
textOff must compare the offset argument against the range
for each text section to determine which one it is in.
The comparison looks like this:

if uintptr(off) >= sectaddr && uintptr(off) <= sectaddr+sectlen

If the off value being compared is equal to sectaddr+sectlen then it
is not within the range of the text section but after it. The
comparison should be just '<'.

Fixes #35210

Change-Id: I114633fd734563d38f4e842dd884c6c239f73c95
Reviewed-on: https://go-review.googlesource.com/c/go/+/203817
Run-TryBot: Lynn Boger 
TryBot-Result: Gobot Gobot 
Reviewed-by: Ian Lance Taylor 
Reviewed-by: Cherry Zhang 
(cherry picked from commit 0ae9389609f23dc905c58fc2ad7bcc16b770f337)
Reviewed-on: https://go-review.googlesource.com/c/go/+/203818
Run-TryBot: Carlos Amedee 
Reviewed-by: Keith Randall

[dev.boringcrypto.go1.12] all: merge go1.12.12 into dev.boringcrypto.go1.12

2019-10-24T10:33:17+00:00

Change-Id: Icb1265898a5da209c1560e2a317e219ceed536af

runtime: fix GDB tests on s390x running Ubuntu 18.04

2019-10-09T15:48:47+00:00

On Ubuntu 18.04 I am seeing GDB fail to restore the stack pointer
during this test because stack unwinding can't find the PC. This CL
is essentially a partial revert of CL 23940 and fixes the issue on
s390x.

Fixes #33757

Change-Id: Ib4c41162dc85dc882eb6e248330f4082c3fa94c3
Reviewed-on: https://go-review.googlesource.com/c/go/+/169857
Run-TryBot: Cherry Zhang 
TryBot-Result: Gobot Gobot 
Reviewed-by: Cherry Zhang 
(cherry picked from commit d91f7e6637cc96029cd5a360a0a74153b39a3ae6)
Reviewed-on: https://go-review.googlesource.com/c/go/+/200039
Run-TryBot: Katie Hockman 
Reviewed-by: Bryan C. Mills 
Reviewed-by: Michael Munday

[dev.boringcrypto.go1.12] all: merge go1.12.5 into dev.boringcrypto.go1.12

2019-05-13T21:40:12+00:00

Change-Id: Ib678f7648515435e990b051579a6dda2e7e6a14e