- 14 Dec, 2011 21 commits
-
-
Brad Fitzpatrick authored
We only want to attempt to un-gzip if there's a body (not in response to a HEAD) This was accidentally passing before, but revealed to be broken when c3c6e72d7cc went in. R=golang-dev, rsc CC=golang-dev https://golang.org/cl/5477093
-
Robert Griesemer authored
benchmark old ns/op new ns/op delta strconv_test.BenchmarkFormatInt 12198 12031 -1.37% strconv_test.BenchmarkAppendInt 9268 9153 -1.24% strconv_test.BenchmarkFormatUint 3538 3429 -3.08% strconv_test.BenchmarkAppendUint 3133 3062 -2.27% No performance difference for GOARCH=amd64. R=golang-dev, rsc CC=golang-dev https://golang.org/cl/5488089
-
Rob Pike authored
Fixes #2163. R=rsc CC=golang-dev https://golang.org/cl/5488068
-
Robert Griesemer authored
benchmark old ns/op new ns/op delta strconv_test.BenchmarkFormatInt 10038 8217 -18.14% strconv_test.BenchmarkAppendInt 6822 4969 -27.16% strconv_test.BenchmarkFormatUint 2811 1814 -35.47% strconv_test.BenchmarkAppendUint 2349 1360 -42.10% R=rsc CC=golang-dev https://golang.org/cl/5488083
-
Robert Griesemer authored
The obvious fix is breaking the build in non-obvious ways. Reverting while waiting for the correct fix, if any is needed. ««« original CL description net/http: fix bug in error checking Thanks to josef86@gmail.com for pointing this out. R=golang-dev, iant CC=golang-dev https://golang.org/cl/5477092 »»» R=iant CC=golang-dev https://golang.org/cl/5488085
-
Robert Griesemer authored
Thanks to josef86@gmail.com for pointing this out. R=golang-dev, iant CC=golang-dev https://golang.org/cl/5477092
-
Luuk van Dijk authored
Fixes #2451 R=rsc, bradfitz CC=golang-dev https://golang.org/cl/5372105
-
Russ Cox authored
R=golang-dev, r CC=golang-dev https://golang.org/cl/5484073
-
Russ Cox authored
R=golang-dev, r CC=golang-dev https://golang.org/cl/5486060
-
Russ Cox authored
The irony! R=golang-dev, r CC=golang-dev https://golang.org/cl/5482062
-
Luuk van Dijk authored
Fixes #2549 R=rsc CC=golang-dev https://golang.org/cl/5484060
-
Luuk van Dijk authored
Cross- and intra package inlining of single assignments or return <expression>. Minus some hairy cases, currently including other calls, expressions with closures and ... arguments. R=rsc, rogpeppe, adg, gri CC=golang-dev https://golang.org/cl/5400043
-
Andrew Balholm authored
Pass tests6.dat, test 13: <button><button> | <html> | <head> | <body> | <button> | <button> Also pass tests through test 25: <table><colgroup>foo R=nigeltao CC=golang-dev https://golang.org/cl/5487072
-
Luuk van Dijk authored
Fixes #2520 R=rsc CC=golang-dev https://golang.org/cl/5482056
-
Luuk van Dijk authored
Fixed issue 2500 R=rsc CC=golang-dev https://golang.org/cl/5485053
-
Russ Cox authored
breaks 64-bit build ««« original CL description 8c: handle 64-bit switch value Cases must still be 32-bit values, but one thing at a time. R=ality, ken2, ken CC=golang-dev https://golang.org/cl/5485063 »»» R=ken2 CC=golang-dev https://golang.org/cl/5488075
-
Christopher Wedgwood authored
(needed for non-zero GOMAXPROCS) R=iant, rsc CC=go.peter.90, golang-dev https://golang.org/cl/5486059
-
Russ Cox authored
Cases must still be 32-bit values, but one thing at a time. R=ality, ken2, ken CC=golang-dev https://golang.org/cl/5485063
-
Rob Pike authored
The transmitter must encode an interface value if it is to be decoded into an interface value, but it's a common and confusing error to encode a concrete value and attempt to decode it into an interface, particularly *interface{}. This CL attempts to explain things better. Fixes #2367. R=golang-dev, rsc CC=golang-dev https://golang.org/cl/5485072
-
Yasuhiro Matsumoto authored
R=golang-dev, alex.brainman CC=golang-dev https://golang.org/cl/5483057
-
Robert Griesemer authored
Not a language change, just stating the facts. Fixes #1793. R=golang-dev, r CC=golang-dev https://golang.org/cl/5488071
-
- 13 Dec, 2011 19 commits
-
-
Joel Sing authored
R=golang-dev, bradfitz CC=golang-dev https://golang.org/cl/5414053
-
Ian Lance Taylor authored
Testing total space fails for gccgo when not using split stacks, because then each goroutine has a large stack, and so the total memory usage is large. R=golang-dev, rsc CC=golang-dev https://golang.org/cl/5487068
-
Rob Pike authored
R=gri, rsc CC=golang-dev https://golang.org/cl/5485067
-
Russ Cox authored
(These are benchmarks for the garbage collector, not tests.) R=golang-dev, adg CC=golang-dev https://golang.org/cl/5484070
-
Russ Cox authored
TBR=r CC=golang-dev https://golang.org/cl/5488066
-
Brad Fitzpatrick authored
R=rsc, r CC=golang-dev https://golang.org/cl/5477084
-
Russ Cox authored
R=golang-dev, r, gri, bradfitz CC=golang-dev https://golang.org/cl/5487067
-
Florian Weimer authored
The golang-dev mailing list is added automatically. R=golang-dev, rsc CC=golang-dev https://golang.org/cl/5482060
-
Russ Cox authored
R=golang-dev, gri CC=golang-dev https://golang.org/cl/5486056
-
Russ Cox authored
I was confused by the existence of two portable Hypot routines in the tree when I cleaned things up, and I made ARM use the wrong (imprecise) one. Use the right one, and delete the wrong one. Fixes arm build. R=golang-dev, r CC=golang-dev https://golang.org/cl/5485065
-
Russ Cox authored
breaks build ««« original CL description http: close connection after printing panic stack trace In a testing situation, it's possible for a local http server to panic and the test exit without the stack trace ever being printed. Fixes #2480. R=rsc, bradfitz CC=golang-dev https://golang.org/cl/5414048 »»» R=bradfitz CC=golang-dev https://golang.org/cl/5482061
-
Robert Griesemer authored
- go/printer: support for printing CommentedNodes - go/doc: collect comments from examples Fixes #2429. R=adg, rsc CC=golang-dev https://golang.org/cl/5482052
-
Robert Griesemer authored
-tabs replaces -tabindent -spaces has been removed R=golang-dev, adg, rsc CC=golang-dev https://golang.org/cl/5487066
-
Andrew Gerrand authored
goinstall: disallow googlecode.com import paths R=rsc, bradfitz CC=golang-dev https://golang.org/cl/5421049
-
Roger Peppe authored
In a testing situation, it's possible for a local http server to panic and the test exit without the stack trace ever being printed. Fixes #2480. R=rsc, bradfitz CC=golang-dev https://golang.org/cl/5414048
-
Yasuhiro Matsumoto authored
R=r, rsc, adg CC=golang-dev https://golang.org/cl/5364056
-
Yasuhiro Matsumoto authored
R=golang-dev, rsc CC=golang-dev https://golang.org/cl/5487057
-
Christopher Wedgwood authored
R=dsymonds CC=golang-dev https://golang.org/cl/5487064
-
Russ Cox authored
This will be nicer to the automatic tools. It requires a few more assembly stubs but fewer Go files. There are a few instances where it looks like there are new blobs of code, but they are just being copied out of deleted files. There is no new code here. Suppose you have a portable implementation for Sin and a 386-specific assembly one. The old way to do this was to write three files sin_decl.go func Sin(x float64) float64 // declaration only sin_386.s assembly implementation sin_port.go func Sin(x float64) float64 { ... } // pure-Go impl and then link in either sin_decl.go+sin_386.s or just sin_port.go. The Makefile actually did the magic of linking in only the _port.go files for those without assembly and only the _decl.go files for those with assembly, or at least some of that magic. The biggest problem with this, beyond being hard to explain to the build system, is that once you do explain it to the build system, godoc knows which of sin_port.go or sin_decl.go are involved on a given architecture, and it (correctly) ignores the other. That means you have to put identical doc comments in both files. The new approach, which is more like what we did in the later packages math/big and sync/atomic, is to have sin.go func Sin(x float64) float64 // decl only func sin(x float64) float64 {...} // pure-Go impl sin_386.s // assembly for Sin (ignores sin) sin_amd64.s // assembly for Sin: jmp sin sin_arm.s // assembly for Sin: jmp sin Once we abandon Makefiles we can put all the assembly stubs in one source file, so the number of files will actually go down. Chris asked whether the branches cost anything. Given that they are branching to pure-Go implementations that are not typically known for their speed, the single direct branch is not going to be noticeable. That is, it's on the slow path. An alternative would have been to preserve the old "only write assembly files when there's an implementation" and still have just one copy of the declaration of Sin (and thus one doc comment) by doing: sin.go func Sin(x float64) float64 { return sin(x) } sin_decl.go func sin(x float64) float64 // declaration only sin_386.s // assembly for sin sin_port.go func sin(x float64) float64 { portable code } In this version everyone would link in sin.go and then either sin_decl.go+sin_386.s or sin_port.go. This has an extra function call on all paths, including the "fast path" to get to assembly, and it triples the number of Go files involved compared to what I did in this CL. On the other hand you don't have to write assembly stubs. After starting down this path I decided that the assembly stubs were the easier approach. As for generating the assembly stubs on the fly, much of the goal here is to eliminate magic from the build process, so that zero-configuration tools like goinstall or the new go tool can handle this package. R=golang-dev, r, cw, iant, r CC=golang-dev https://golang.org/cl/5488057
-