- 15 Jul, 2015 19 commits
-
-
Russ Cox authored
Also use more consistent language for the new build options. Change-Id: I88cbe200c13f452713be73d2e00337ddb793b8c6 Reviewed-on: https://go-review.googlesource.com/12172Reviewed-by: Rob Pike <r@golang.org>
-
Russ Cox authored
Fixes #10210. Change-Id: I82ddd665bca31773b1fb1b056338c04818ef68f5 Reviewed-on: https://go-review.googlesource.com/12171Reviewed-by: Rob Pike <r@golang.org>
-
Russ Cox authored
Also adds to 'go test' all the build flags that were missing due to inconsistency in the duplication (for example, -toolexec). Fixes #10504. Change-Id: I1935b5caa13d5e551a0483904adffa8877087df7 Reviewed-on: https://go-review.googlesource.com/12170Reviewed-by: Rob Pike <r@golang.org>
-
Russ Cox authored
Fixes #9853. Change-Id: Ic4803aa499ca20215085a87bad649014984d84c8 Reviewed-on: https://go-review.googlesource.com/12149Reviewed-by: Rob Pike <r@golang.org>
-
Russ Cox authored
While we are here, fix a few things not updated for -insecure. Fixes #8163. Change-Id: Ib80c9ac00d6b61cce26c3d20bee3d30ab9af1331 Reviewed-on: https://go-review.googlesource.com/12148Reviewed-by: Rob Pike <r@golang.org>
-
Russ Cox authored
Was detecting only non-trivial ones. Fixes #9690. Change-Id: I662d81dd4818ddf29592057c090805772c84287b Reviewed-on: https://go-review.googlesource.com/12147Reviewed-by: Rob Pike <r@golang.org>
-
Russ Cox authored
This reverts commit 3b411bf1a1bb08d6868083981cecba8088dc7aea. Change-Id: I321a43fa378a43b3e4d7aa97e0222775640af64b Reviewed-on: https://go-review.googlesource.com/12205Reviewed-by: Russ Cox <rsc@golang.org>
-
Russ Cox authored
These used to be defined at use, but that breaks when shared libraries are involved. For #11480. Change-Id: I416a848754fb615c0d75f9f0ccc00723d07f7f01 Reviewed-on: https://go-review.googlesource.com/12145Reviewed-by: Rob Pike <r@golang.org>
-
Russ Cox authored
When the prologue call to morestack was moved down to the bottom of the function, the pc/sp tables were not updated. If a traceback through a call to morestack is needed, it would get confused at and stop at morestack. Confirmed the fix by adding //go:systemstack (which calls morestackc, but same issue) where it did not belong and inspecting the crash. Change-Id: Id0294bb9dba51ef1a49154637228fb57f1086a94 Reviewed-on: https://go-review.googlesource.com/12144Reviewed-by: Rob Pike <r@golang.org>
-
Jeff R. Allen authored
A malformed Host header can result in a malformed HTTP request. Clean them to avoid this. Updates #11206. We may come back and make this stricter for 1.6. Change-Id: I23c7d821cd9dbf66c3c15d26750f305e3672d984 Reviewed-on: https://go-review.googlesource.com/11241Reviewed-by: Russ Cox <rsc@golang.org>
-
David du Colombier authored
The interface to set TCP keepalive on Plan 9 is writing the "keepalive n" string to the TCP ctl file, where n is the milliseconds between keepalives. Fixes #11266. Change-Id: Ic96f6c584063665a1ddf921a9a4ddfa13cc7501b Reviewed-on: https://go-review.googlesource.com/11860 Run-TryBot: David du Colombier <0intro@gmail.com> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Russ Cox <rsc@golang.org>
-
Rob Pike authored
Update #10096 Arm64 and Ppc64 are still pretty sketchy. Change-Id: Iaf821b0f17bad8c71d338d45de75d4a345cac2dd Reviewed-on: https://go-review.googlesource.com/12160Reviewed-by: Russ Cox <rsc@golang.org>
-
Robert Griesemer authored
When testing if a value is an integer, if the value is a constant, don't ignore the type if it has one. Fixes #11594. Change-Id: I2ff387e4f9e8ab7cae35c4838350e0a1fce2e625 Reviewed-on: https://go-review.googlesource.com/12045Reviewed-by: Alan Donovan <adonovan@google.com>
-
Didier Spezia authored
When building a directive, the current sanity check prevents a '>' to be used, which makes a DOCTYPE directive with an internal subset be rejected. It is accepted by the parser though, so what can be parsed cannot be encoded. Improved the corresponding sanity check to mirror the behavior of the parser (in the way it handles angle brackets, quotes, and comments). Fixes #10158 Change-Id: Ieffea9f870f2694548e12897f8f47babc0ea4414 Reviewed-on: https://go-review.googlesource.com/11630Reviewed-by: Russ Cox <rsc@golang.org>
-
Jonathan Rudenberg authored
- Fix incomplete description of minimum protocol version. - Add mention of the new ConnectionState.OCSPResponse field. - Clarify session ticket key rotation description. Change-Id: I6b62d30a4d0e0f84fd2c0e70e8f66ec14e6a5a90 Reviewed-on: https://go-review.googlesource.com/12197Reviewed-by: Rob Pike <r@golang.org>
-
Brad Fitzpatrick authored
Includes subrepos and some special cases. Updates #10639 Change-Id: I3c9ad4f6ec689903f88ccf5599d93a338e3eec4d Reviewed-on: https://go-review.googlesource.com/12211Reviewed-by: Andrew Gerrand <adg@golang.org>
-
Larz Conwell authored
The "string" option only applies for strings, floats, integers, and booleans as per the documentation. So when decoding ignore the "string" option if the value is not of one of the types mentioned. This matches the Marshal step which also ignores the "string" option for invalid types. Fixes #9812 Change-Id: I0fb2b43d0668bc0e2985886d989abbf2252070e2 Reviewed-on: https://go-review.googlesource.com/10183Reviewed-by: Russ Cox <rsc@golang.org>
-
Brad Fitzpatrick authored
This is an automated update for the main branch of the main repo. Some special cases and other repos will follow. Updates #10639 Change-Id: I4b149c037e9292b7e323a9f4c009092ce6b70ce5 Reviewed-on: https://go-review.googlesource.com/12159Reviewed-by: Andrew Gerrand <adg@golang.org>
-
Jonathan Rudenberg authored
This is the first mention of the fmt package in the changes list. Change-Id: I5d378d8707e6735e0e590527db4196b517fefd72 Reviewed-on: https://go-review.googlesource.com/12198Reviewed-by: Andrew Gerrand <adg@golang.org>
-
- 14 Jul, 2015 11 commits
-
-
Jonathan Rudenberg authored
Change-Id: I8bbdf6c769e089fca8458166dffff5aea0f74675 Reviewed-on: https://go-review.googlesource.com/12196Reviewed-by: Andrew Gerrand <adg@golang.org>
-
Nevins Bartolomeo authored
Change-Id: Ifbab8203dea1eb0df4c834df22e12cb7c37c14fd Reviewed-on: https://go-review.googlesource.com/10683Reviewed-by: Adam Langley <agl@golang.org> Run-TryBot: Russ Cox <rsc@golang.org>
-
David Crawshaw authored
Fixes #9769. Change-Id: I2959906c71d0ce62cdb750dab78eab631a26f229 Reviewed-on: https://go-review.googlesource.com/12080Reviewed-by: Rob Pike <r@golang.org> Reviewed-by: Russ Cox <rsc@golang.org>
-
Ian Lance Taylor authored
Fixes #10193. Change-Id: Ibbb747babb697a66b943e5da76b0ada41f1fb14f Reviewed-on: https://go-review.googlesource.com/12070 Run-TryBot: Ian Lance Taylor <iant@golang.org> Reviewed-by: Russ Cox <rsc@golang.org>
-
Ian Lance Taylor authored
Fixes #11704. Change-Id: If103f8eca7e53b0120885e2ec086db12176ea078 Reviewed-on: https://go-review.googlesource.com/12155Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
-
Nigel Tao authored
This rolls back most of golang.org/cl/8841, aka 2f98bac3, and makes a different fix. It keeps the TestTruncatedSOSDataDoesntPanic test introduced by that other CL, which obviously still passes after this CL. Fixes #11650, a regression (introduced by cl/8841) from Go 1.4. The original cl/8841 changed the image/jpeg not to panic on an input given in #10387. We still do not panic on that input, after this CL. I have a corpus of over 160,000 JPEG images, a sample of a web crawl. The image/jpeg code ran happily over that whole corpus both before and after this CL, although that corpus clearly didn't catch the regression in the first place. This code was otherwise tested manually. I don't think that it's trivial to synthesize a JPEG input that happens to run out of Huffman data at just the right place. The test image attached to #11650 obviously has that property, but I don't think we can simply add that test image to the repository: it's 227KiB, and I don't know its copyright status. I also looked back over the issue tracker for problematic JPEGs that people have filed. The Go code, after this CL, is still happy on these files in my directory: issue2362a.jpeg issue3916.jpeg issue3976.jpeg issue4084.jpeg issue4259.jpeg issue4291.jpeg issue4337.jpeg issue4500.jpeg issue4705.jpeg issue4975.jpeg issue5112.jpeg issue6767.jpeg issue9888.jpeg issue10133.jpeg issue10357.jpeg issue10447.jpeg issue11648.jpeg issue11650.jpeg There were other images attached in the issue tracker that aren't actually valid JPEGs. They failed both before and after this CL: broken-issue2362b.jpeg broken-issue6450.jpeg broken-issue8693.jpeg broken-issue10154.jpeg broken-issue10387.jpeg broken-issue10388.jpeg broken-issue10389.jpeg broken-issue10413.jpeg In summary, this CL fixes #11650 and, after some automated and manual testing, I don't think introduces new regressions. Change-Id: I30b67036e9b087f3051d57dac7ea05fb4fa36f66 Reviewed-on: https://go-review.googlesource.com/12163Reviewed-by: Rob Pike <r@golang.org>
-
Rob Pike authored
Change-Id: I7ad90ab78abb8a39d56c837610d5c311a96b7039 Reviewed-on: https://go-review.googlesource.com/12162Reviewed-by: Nigel Tao <nigeltao@golang.org>
-
Brad Fitzpatrick authored
Fixes build from https://golang.org/cl/12152 Plan 9 lacks syscall.EPIPE. I was misled by api/go1.txt and also forgot to use the trybots. :( Change-Id: I4982fe969ad4a8724090cb03009bfb21780d8aa7 Reviewed-on: https://go-review.googlesource.com/12153 Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org> Reviewed-by: Rob Pike <r@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org>
-
Ross Light authored
Add tests for isSecure function. Change-Id: I49de9d2846b75d4c7be745484f85d351a6fd851d Reviewed-on: https://go-review.googlesource.com/11514Reviewed-by: Russ Cox <rsc@golang.org>
-
Russ Cox authored
Fixes #11656 (again). Change-Id: I170ff10bfbdb0f34e57c11de42b6ee5291837813 Reviewed-on: https://go-review.googlesource.com/12142Reviewed-by: Russ Cox <rsc@golang.org>
-
Brad Fitzpatrick authored
Fixes #9173 Change-Id: I83530533db84b07cb88dbf6ec690be48a06a9d7d Reviewed-on: https://go-review.googlesource.com/12152Reviewed-by: Ian Lance Taylor <iant@golang.org>
-
- 13 Jul, 2015 10 commits
-
-
Rob Pike authored
Still to do: ARM64 and PPC64. These architectures are woefully underdocumented. Change-Id: Iedcf767a7e0e1c931812351940bc08f0c3821212 Reviewed-on: https://go-review.googlesource.com/12110Reviewed-by: Russ Cox <rsc@golang.org>
-
Rob Pike authored
The old numerical names like 6.out.go are a relic from the old tools. Easier to rename than explain. The anames.go files were modified by go generate; no changes beyond the explanatory comment at the top. Change-Id: I84742c75c60e47724baa9d49a91fef1f8581f021 Reviewed-on: https://go-review.googlesource.com/12069 Run-TryBot: Rob Pike <r@golang.org> Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org> Reviewed-by: Russ Cox <rsc@golang.org>
-
Austin Clements authored
These memstats are currently being computed by gcMark, which was appropriate in Go 1.4, but gcMark is now just one part of a bigger picture. In particular, it can't account for the sweep termination pause time, it can't account for all of the mark termination pause time, and the reported "pause end" and "last GC" times will be slightly earlier than they really are. Lift computing of these statistics into func gc, which has the appropriate visibility into the process to compute them correctly. Fixes one of the issues in #10323. This does not add new statistics appropriate to the concurrent collector; it simply fixes existing statistics that are being misreported. Change-Id: I670cb16594a8641f6b27acf4472db15b6e8e086e Reviewed-on: https://go-review.googlesource.com/11794Reviewed-by: Russ Cox <rsc@golang.org>
-
Austin Clements authored
Currently we report MemStats.PauseEnd in nanoseconds, but with no particular 0 time. On Linux, the 0 time is when the host started. On Darwin, it's the UNIX epoch. This is also inconsistent with the other absolute time in MemStats, LastGC, which is always reported in nanoseconds since 1970. Fix PauseEnd so it's always reported in nanoseconds since 1970, like LastGC. Fixes one of the issues raised in #10323. Change-Id: Ie2fe3169d45113992363a03b764f4e6c47e5c6a8 Reviewed-on: https://go-review.googlesource.com/11801 Run-TryBot: Austin Clements <austin@google.com> Reviewed-by: Russ Cox <rsc@golang.org>
-
Russ Cox authored
Fixes #11656. Change-Id: Ib81d583e4b004e67dc9d2f898fd798112434e7a9 Reviewed-on: https://go-review.googlesource.com/12026Reviewed-by: Ian Lance Taylor <iant@golang.org> Run-TryBot: Russ Cox <rsc@golang.org>
-
Russ Cox authored
Fixes race detector build. Change-Id: I8bdc78d57487580e6b5b8c415df4653a1ba69e37 Reviewed-on: https://go-review.googlesource.com/12087Reviewed-by: Austin Clements <austin@google.com>
-
Mikio Hara authored
This change does clean up as preparation for fixing #11081. - renames cfg to resolvConf for clarification - adds a new type resolverConfig and its methods: init, update, tryAcquireSema, releaseSema for mutual exclusion of resolv.conf data - deflakes, simplifies tests for resolv.conf data; previously the tests sometimes left some garbage in the data Change-Id: I277ced853fddc3791dde40ab54dbd5c78114b78c Reviewed-on: https://go-review.googlesource.com/10931Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org> Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org>
-
Russ Cox authored
Fixes #11307. Fixes #11055. Change-Id: I8d6b04cb509e62e27d6935b91ffe35fdaea4ebcd Reviewed-on: https://go-review.googlesource.com/12028Reviewed-by: Ian Lance Taylor <iant@golang.org> Reviewed-by: Andrew Gerrand <adg@golang.org>
-
Russ Cox authored
Missed select case when adding the barrier last time. All the more reason to refactor this code in Go 1.6. Fixes #11643. Change-Id: Ib0d19d6e0939296c0a3e06dda5e9b76f813bbc7e Reviewed-on: https://go-review.googlesource.com/12086Reviewed-by: Austin Clements <austin@google.com>
-
Alan Donovan authored
This is a copy of an upstream change to the tools repo: https://go-review.googlesource.com/#/c/8924/ This is a second attempt at CL 8954, with the necessary change to go/build's deps test. Change-Id: Ib798498cf85fea0baec5667e9324d11f6ae8ad64 Reviewed-on: https://go-review.googlesource.com/9173Reviewed-by: Robert Griesemer <gri@golang.org> Reviewed-by: Russ Cox <rsc@golang.org>
-