From: Russ Cox <rsc@golang.org>
Date: Thu, 7 Jan 2016 02:28:06 +0000 (-0500)
Subject: doc: mention that Go no longer calls timeBeginPeriod(1) on Windows
X-Git-Tag: go1.6beta2~95
X-Git-Url: http://www.git.cypherpunks.su/?a=commitdiff_plain;h=f962fc0820f13d6a44b8ef88e0fe20c02123b1b2;p=gostls13.git

doc: mention that Go no longer calls timeBeginPeriod(1) on Windows

Fixes #13731.

Change-Id: Iaf70a8b41c947f0d86013808564112ab676136e3
Reviewed-on: https://go-review.googlesource.com/18345
Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
Reviewed-by: Alex Brainman <alex.brainman@gmail.com>
---

diff --git a/doc/go1.6.html b/doc/go1.6.html
index 9192ca0c61..3ae96b82a9 100644
--- a/doc/go1.6.html
+++ b/doc/go1.6.html
@@ -332,6 +332,15 @@ Searching for uses of
 <a href="/pkg/os/signal/#Notify"><code>signal.Notify</code></a> may help identify such code.
 </p>
 
+<p>
+On Windows, Go programs in Go 1.5 and earlier forced
+the global Windows timer resolution to 1ms at startup
+by calling <code>timeBeginPeriod(1)</code>.
+Go no longer needs this for good scheduler performance,
+and changing the global timer resolution caused problems on some systems,
+so the call has been removed.
+</p>
+
 <h3 id="reflect">Reflect</h3>
 
 <p>