- 17 Jul, 2013 1 commit
-
-
Dave Cheney authored
Replaced with something more appropriate. R=adg, r, minux.ma CC=golang-dev https://golang.org/cl/11421043
-
- 16 Jul, 2013 20 commits
-
-
Keith Randall authored
R=golang-dev, rsc CC=golang-dev https://golang.org/cl/11385045
-
Adam Langley authored
(PSS support is complete.) Thanks to Frithjof Schulze for noting this. R=golang-dev, r CC=golang-dev https://golang.org/cl/10871046
-
Ian Lance Taylor authored
R=golang-dev, remyoudompheng CC=golang-dev https://golang.org/cl/11379044
-
Adam Langley authored
R=golang-dev, rsc CC=golang-dev https://golang.org/cl/11386043
-
Russ Cox authored
If calling a function in package runtime, emit argument size information around the call in case the call is to a variadic C function. R=ken2 CC=golang-dev https://golang.org/cl/11371043
-
Russ Cox authored
R=ken2 CC=golang-dev https://golang.org/cl/11364043
-
Russ Cox authored
I have not done the system call stubs in sys_*.s. I hope to avoid that, because those do not block, so those frames will not appear in stack traces during garbage collection. R=golang-dev, dvyukov, khr CC=golang-dev https://golang.org/cl/11360043
-
Russ Cox authored
While we're here, fix Syscall9 on NetBSD and OpenBSD: it was storing the results into the wrong memory locations. I guess no one uses that function's results on those systems. Part of cleaning up stack traces and argument frame information. R=golang-dev, dvyukov CC=golang-dev https://golang.org/cl/11355044
-
Russ Cox authored
In cmd/5a, also add support for argument size in TEXT instruction. R=ken2 CC=golang-dev https://golang.org/cl/11357044
-
Russ Cox authored
The portable code in cmd/ld already knows how to process it, we just have to ignore it during code generation. R=ken2 CC=golang-dev https://golang.org/cl/11363043
-
Alan Donovan authored
R=gri CC=golang-dev https://golang.org/cl/11359043
-
Dmitriy Vyukov authored
R=golang-dev, iant CC=golang-dev https://golang.org/cl/11357043
-
Joel Sing authored
s/TCP_KEEPALIVE/SO_KEEPALIVE/ to unbreak build on OpenBSD. R=golang-dev, iant CC=golang-dev https://golang.org/cl/11345044
-
Russ Cox authored
Design at http://golang.org/s/go12symtab. This enables some cleanup of the garbage collector metadata that will be done in future CLs. This CL does not move the old symtab and pclntab back into an unmapped section of the file. That's a bit tricky and will be done separately. Fixes #4020. R=golang-dev, dave, cshapiro, iant, r CC=golang-dev, nigeltao https://golang.org/cl/11085043
-
Dmitriy Vyukov authored
Race instrumentation can allocate, switch stacks, preempt, etc. All that is not allowed in between fork and exec. Fixes #4840. R=golang-dev, daniel.morsing, dave CC=golang-dev https://golang.org/cl/11324044
-
Daniel Morsing authored
Fixes #5358. R=golang-dev, rsc CC=golang-dev https://golang.org/cl/11282044
-
Evan Shaw authored
R=golang-dev, r CC=golang-dev https://golang.org/cl/11334043
-
Rémy Oudompheng authored
A type switch on a value with map index expressions, could get a spurious instrumentation from a OTYPESW node. These nodes do not need instrumentation because after walk the type switch has been turned into a sequence of ifs. Fixes #5890. R=golang-dev, dvyukov CC=golang-dev https://golang.org/cl/11308043
-
Alex Brainman authored
Fixes #5831 R=golang-dev, rsc CC=golang-dev https://golang.org/cl/11266043
-
Russ Cox authored
"M requires pointer receiver" can be misinterpreted to mean that method M should have a pointer receiver but does not. In fact the message means "M has a pointer receiver" (and you don't have a pointer). Fixes #5891. R=ken2 CC=golang-dev https://golang.org/cl/11313043
-
- 15 Jul, 2013 8 commits
-
-
David Presotto authored
Sets both the duration from the last data packet to the first keep alive packet and the duration between keep alive packets to be the passed duration. I've tested the function on both Darwin (10.8.4) and 4.2 Linux. I've compiled (make.bash) for all the OS's and tested (all.bash) on Darwin and Linux. R=golang-dev, dave, rsc, dvyukov, presotto+facebook, nick CC=golang-dev, veyron-team https://golang.org/cl/11130044
-
Russ Cox authored
R=golang-dev, r CC=golang-dev https://golang.org/cl/11299043
-
Dmitriy Vyukov authored
R=golang-dev, khr, rsc CC=golang-dev https://golang.org/cl/11280043
-
Shenghou Ma authored
see issue 5885. R=golang-dev, iant CC=golang-dev https://golang.org/cl/10914045
-
Andrew Bonventre authored
R=r, nigeltao CC=golang-dev https://golang.org/cl/10896043
-
Alexandre Normand authored
The postinstall script causes the installation to fail because the last step that copies files for Xcode is broken. Two details can cause the command to fail: 1. The XCODE_MISC_DIR value has a space. Without quotes in the cp command, cp will just complain that this is an invalid syntax. 2. The source of the cp is a directory with two subdirectories. We actually want the files for either Xcode 3 or Xcode 4 to be copied. Using xcodebuild -version, we check for the Xcode version and select which of xcode/3/* or xcode/4/* should be the source of the copy. Fixes #5874. R=golang-dev, minux.ma, adg CC=golang-dev https://golang.org/cl/10893044
-
Andrew Gerrand authored
Generated by addca. R=gobot CC=golang-dev https://golang.org/cl/11257043
-
Nigel Tao authored
R=dsymonds CC=golang-dev https://golang.org/cl/11256043
-
- 14 Jul, 2013 2 commits
-
-
Joseph Holsten authored
R=golang-dev, r CC=golang-dev https://golang.org/cl/11220044
-
Rob Pike authored
Generated by addca. R=gobot CC=golang-dev https://golang.org/cl/11245043
-
- 13 Jul, 2013 3 commits
-
-
Russ Cox authored
Pointed out by khr. R=ken2 CC=golang-dev https://golang.org/cl/11145044
-
Russ Cox authored
Suggested by Rob in CL 11211045, but the mail arrived moments after hg submit completed. R=golang-dev, r CC=golang-dev https://golang.org/cl/11138045
-
Russ Cox authored
Before: $ go test -c -cover fmt $ ./fmt.test -test.covermode=set PASS coverage: 65.1% of statements in strconv $ After: $ go test -c -cover fmt $ ./fmt.test PASS coverage: 65.1% of statements in strconv $ In addition to being cumbersome, the old flag didn't make sense: the cover mode cannot be changed after the binary has been built. Another useful effect of this CL is that if you happen to do $ go test -c -covermode=atomic fmt and then forget you did that and run benchmarks, the final line of the output (the coverage summary) reminds you that you are benchmarking with coverage enabled, which might not be what you want. $ ./fmt.test -test.bench . PASS BenchmarkSprintfEmpty 10000000 217 ns/op BenchmarkSprintfString 2000000 755 ns/op BenchmarkSprintfInt 2000000 774 ns/op BenchmarkSprintfIntInt 1000000 1363 ns/op BenchmarkSprintfPrefixedInt 1000000 1501 ns/op BenchmarkSprintfFloat 1000000 1257 ns/op BenchmarkManyArgs 500000 5346 ns/op BenchmarkScanInts 1000 2562402 ns/op BenchmarkScanRecursiveInt 500 3189457 ns/op coverage: 91.4% of statements $ As part of passing the new mode setting in via _testmain.go, merge the two registration mechanisms into one extensible mechanism (a struct). R=r CC=golang-dev https://golang.org/cl/11219043
-
- 12 Jul, 2013 6 commits
-
-
Russ Cox authored
I want to think more carefully about this. We put this in because Marshal encoded named []byte but Unmarshal rejected them. And we noticed that Marshal's behavior was undocumented so we documented it. But I am starting to think the docs and Unmarshal were correct and Marshal's behavior was the problem. Rolling back to give us more time to think. ««« original CL description json: unmarshal types that are byte slices. The json package cheerfully would marshal type S struct { IP net.IP } but would give an error when unmarshalling. This change allows any type whose concrete type is a byte slice to be unmarshalled from a string. Fixes #5086. R=golang-dev, rsc CC=golang-dev https://golang.org/cl/11161044 »»» R=golang-dev, r CC=golang-dev https://golang.org/cl/11042046
-
Russ Cox authored
In practice, rejecting an entire structure due to a single invalid byte in a string is just too picky, and too hard to track down. Be consistent with the bulk of the standard library by converting invalid UTF-8 into UTF-8 with replacement runes. R=golang-dev, crawshaw CC=golang-dev https://golang.org/cl/11211045
-
Keith Randall authored
R=golang-dev, rsc CC=golang-dev https://golang.org/cl/11056044
-
Russ Cox authored
go tool 6a -$(unicode fffd) was crashing. Fixes #5878. R=ken2 CC=golang-dev https://golang.org/cl/11208045
-
Shenghou Ma authored
Recently addition to runtime test makes it take very close to 720s of timeout limit on the netbsd-arm-qemu builder. R=golang-dev, go.peter.90, rsc CC=golang-dev https://golang.org/cl/10935043
-
Russ Cox authored
Deferred functions are not run by a call instruction. They are run by the runtime editing registers to make the call start with a caller PC returning to a CALL deferreturn instruction. That instruction has always had the line number of the function's closing brace, but that instruction's line number is irrelevant. Stack traces show the line number of the instruction before the return PC, because normally that's what started the call. Not so here. The instruction before the CALL deferreturn could be almost anywhere in the function; it's unrelated and its line number is incorrect to show. Fix the line number by inserting a true hardware no-op with the right line number before the returned-to CALL instruction. That is, the deferred calls now appear to start with a caller PC returning to the second instruction in this sequence: NOP CALL deferreturn The traceback will show the line number of the NOP, which we've set to be the line number of the function's closing brace. The NOP here is not the usual pseudo-instruction, which would be elided by the linker. Instead it is the real hardware instruction: XCHG AX, AX on 386 and amd64, and AND.EQ R0, R0, R0 on ARM. Fixes #5856. R=ken2, ken CC=golang-dev https://golang.org/cl/11223043
-