- 15 Nov, 2013 1 commit
-
-
Brad Fitzpatrick authored
R=golang-dev, crawshaw CC=golang-dev https://golang.org/cl/27000043
-
- 14 Nov, 2013 2 commits
-
-
Russ Cox authored
Also rename URL to /doc/asm. R=golang-dev, minux.ma, r CC=golang-dev https://golang.org/cl/26170043
-
Russ Cox authored
This seems to be the best of a long list of bad ways to fix this issue. Fixes #6760. R=r CC=golang-dev https://golang.org/cl/22770044
-
- 13 Nov, 2013 7 commits
-
-
Andrew Gerrand authored
R=golang-dev, r CC=golang-dev https://golang.org/cl/26220045
-
Andrew Gerrand authored
R=golang-dev, dsymonds CC=golang-dev https://golang.org/cl/25580045
-
Rob Pike authored
Blocked on 20930043, the CL the new text references. R=golang-dev, bradfitz CC=golang-dev https://golang.org/cl/18430044
-
Rob Pike authored
Fixes #6060 R=golang-dev, iant, bradfitz, josharian, minux.ma, aram, rsc CC=golang-dev https://golang.org/cl/20930043
-
Robert Griesemer authored
This documents the status quo more precisely. Not a language change. Fixes #6006. R=r, rsc, iant, ken CC=golang-dev https://golang.org/cl/14415043
-
Andrew Gerrand authored
I used "and above" when I should have said "or later". Sorry for the churn. R=golang-dev, bradfitz CC=golang-dev https://golang.org/cl/25670043
-
Andrew Gerrand authored
R=golang-dev, r CC=golang-dev https://golang.org/cl/25370045
-
- 12 Nov, 2013 2 commits
-
-
Robert Griesemer authored
R=adonovan CC=golang-dev https://golang.org/cl/25360043
-
Robert Griesemer authored
Generated by addca. R=gobot CC=golang-dev https://golang.org/cl/25350043
-
- 11 Nov, 2013 2 commits
-
-
David Crawshaw authored
R=dsymonds, dominik.honnef, n13m3y3r, rsc, kamil.kisiel CC=golang-dev https://golang.org/cl/22940044
-
Olivier Duperray authored
Fixes issue 5807 . R=golang-dev, adg CC=golang-dev https://golang.org/cl/23940043
-
- 08 Nov, 2013 2 commits
-
-
Dominik Honnef authored
- Use #' for function symbols - Remove unused variables - Use declare-function to shut up byte compiler This is identical to CL 19010044 with one exception: Making sure it doesn't break on Emacs 22.1 R=adonovan, bradfitz, shendaras CC=golang-dev https://golang.org/cl/20100043
-
Sameer Ajmani authored
R=adonovan CC=golang-dev https://golang.org/cl/23680043
-
- 07 Nov, 2013 1 commit
-
-
Russ Cox authored
Clang does not record the "size" field for pointer types, so we must insert the size ourselves. We were already doing this, but only for the case of pointer types. For an array of pointer types, the setting of the size for the nested pointer type was happening after the computation of the size of the array type, meaning that the array type was always computed as 0 bytes. Delay the size computation. This bug happens on all Clang systems, not just FreeBSD. Our test checked that cgo wrote something, not that it was correct. FreeBSD's default clang rejects array[0] as a C struct field, so it noticed the incorrect sizes. But the sizes were incorrect everywhere. Update testcdefs to check the output has the right semantics. Fixes #6292. R=golang-dev, iant CC=golang-dev https://golang.org/cl/22840043
-
- 06 Nov, 2013 1 commit
-
-
Ian Lance Taylor authored
R=golang-dev, minux.ma CC=golang-dev https://golang.org/cl/22510043
-
- 05 Nov, 2013 3 commits
-
-
Ato Araki authored
This fix will show a good synopsis on package listings in that languages. R=adg, r CC=golang-dev https://golang.org/cl/21130043
-
Andrew Gerrand authored
Generated by addca. R=gobot CC=golang-dev https://golang.org/cl/21790043
-
Andrew Gerrand authored
I know it's linked in the previous sentence, but this new link is where I want it to be while reading this sentence. R=golang-dev, bradfitz CC=golang-dev https://golang.org/cl/21770043
-
- 04 Nov, 2013 2 commits
-
-
Brad Fitzpatrick authored
Fixes #6712 R=golang-dev, adg, rsc CC=golang-dev https://golang.org/cl/21450043
-
Andrew Gerrand authored
R=golang-dev CC=golang-dev https://golang.org/cl/21390044
-
- 01 Nov, 2013 2 commits
-
-
Brad Fitzpatrick authored
R=golang-dev, rsc CC=golang-dev https://golang.org/cl/19990045
-
Andrew Gerrand authored
R=golang-dev, dsymonds CC=golang-dev https://golang.org/cl/20680043
-
- 31 Oct, 2013 2 commits
-
-
Russ Cox authored
Two bugs: 1. The first iteration of the traceback always uses LR when provided, which it is (only) during a profiling signal, but in fact LR is correct only if the stack frame has not been allocated yet. Otherwise an intervening call may have changed LR, and the saved copy in the stack frame should be used. Fix in traceback_arm.c. 2. The division runtime call adds 8 bytes to the stack. In order to keep the traceback routines happy, it must copy the saved LR into the new 0(SP). Change SUB $8, SP into MOVW 0(SP), R11 // r11 is temporary, for use by linker MOVW.W R11, -8(SP) to update SP and 0(SP) atomically, so that the traceback always sees a saved LR at 0(SP). Fixes #6681. R=golang-dev, r CC=golang-dev https://golang.org/cl/19910044
-
Russ Cox authored
The CL causes misc/cgo/test to fail randomly. I suspect that the problem is the use of a division instruction in usleep, which can be called while trying to acquire an m and therefore cannot store the denominator in m. The solution to that would be to rewrite the code to use a magic multiply instead of a divide, but now we're getting pretty far off the original code. Go back to the original in preparation for a different, less efficient but simpler fix. ««« original CL description cmd/5l, runtime: make ARM integer division profiler-friendly The implementation of division constructed non-standard stack frames that could not be handled by the traceback routines. CL 13239052 left the frames non-standard but fixed them for the specific case of a divide-by-zero panic. A profiling signal can arrive at any time, so that fix is not sufficient. Change the division to store the extra argument in the M struct instead of in a new stack slot. That keeps the frames bog standard at all times. Also fix a related bug in the traceback code: when starting a traceback, the LR register should be ignored if the current function has already allocated its stack frame and saved the original LR on the stack. The stack copy should be used, as the LR register may have been modified. Combined, these make the torture test from issue 6681 pass. Fixes #6681. R=golang-dev, r, josharian CC=golang-dev https://golang.org/cl/19810043 »»» TBR=r CC=golang-dev https://golang.org/cl/20350043
-
- 30 Oct, 2013 6 commits
-
-
Russ Cox authored
The implementation of division constructed non-standard stack frames that could not be handled by the traceback routines. CL 13239052 left the frames non-standard but fixed them for the specific case of a divide-by-zero panic. A profiling signal can arrive at any time, so that fix is not sufficient. Change the division to store the extra argument in the M struct instead of in a new stack slot. That keeps the frames bog standard at all times. Also fix a related bug in the traceback code: when starting a traceback, the LR register should be ignored if the current function has already allocated its stack frame and saved the original LR on the stack. The stack copy should be used, as the LR register may have been modified. Combined, these make the torture test from issue 6681 pass. Fixes #6681. R=golang-dev, r, josharian CC=golang-dev https://golang.org/cl/19810043
-
Rob Pike authored
TBR=rsc R=golang-dev CC=golang-dev https://golang.org/cl/19840043
-
Rob Pike authored
R=golang-dev, minux.ma, adg, rsc CC=golang-dev https://golang.org/cl/19600043
-
Russ Cox authored
The current Windows build breakage appears to be because the Windows code should be looking for __cgodebug_data not ___cgodebug_data. Dodge the question everywhere by accepting both. R=golang-dev, iant CC=golang-dev https://golang.org/cl/19780043
-
Alan Donovan authored
bradfitz reports: > It breaks go-mode on GNU Emacs 22.1.1 as ships with OS X 10.8.6. ««« original CL description misc/emacs: various cleanups - Use #' for function symbols - Remove unused variables - Use declare-function to shut up byte compiler R=adonovan CC=golang-dev https://golang.org/cl/19010044 »»» R=bradfitz CC=golang-dev https://golang.org/cl/19640043
-
Brad Fitzpatrick authored
Fixes #5110 R=golang-dev, r CC=golang-dev https://golang.org/cl/19280046
-
- 29 Oct, 2013 7 commits
-
-
Julien Schmidt authored
R=golang-dev CC=bradfitz, golang-dev https://golang.org/cl/17590043
-
David Symonds authored
R=golang-dev CC=golang-dev https://golang.org/cl/19510043
-
Russ Cox authored
Most Unix systems have their own time zone data, so we almost never get far enough in the list to discover that we cannot fall back to the zip file. Adjust testing to exercise the final fallback. Plan 9 and Windows were already correct (and are the main users of the zip file). R=golang-dev, bradfitz CC=golang-dev https://golang.org/cl/19280043
-
Russ Cox authored
The tag is ",chardata" not "chardata". Fixes #6631. R=golang-dev, bradfitz CC=golang-dev https://golang.org/cl/19300046
-
Brad Fitzpatrick authored
Fixes #6471 R=golang-dev, rsc CC=golang-dev https://golang.org/cl/14920050
-
Dominik Honnef authored
- Use #' for function symbols - Remove unused variables - Use declare-function to shut up byte compiler R=adonovan CC=golang-dev https://golang.org/cl/19010044
-
Russ Cox authored
This CL restores the Go 1.1.2 semantics for os.File's Readdir method. The code in Go 1.1.2 was rewritten mainly because it looked buggy. This new version attempts to be clearer but still provide the 1.1.2 results. The important diff is not this CL's version against tip but this CL's version against Go 1.1.2. Go 1.1.2: names, err := f.Readdirnames(n) fi = make([]FileInfo, len(names)) for i, filename := range names { fip, err := Lstat(dirname + filename) if err == nil { fi[i] = fip } else { fi[i] = &fileStat{name: filename} } } return fi, err This CL: names, err := f.Readdirnames(n) fi = make([]FileInfo, len(names)) for i, filename := range names { fip, lerr := lstat(dirname + filename) if lerr != nil { fi[i] = &fileStat{name: filename} continue } fi[i] = fip } return fi, err The changes from Go 1.1.2 are stylistic, not semantic: 1. Use lstat instead of Lstat, for testing (done before this CL). 2. Make error handling in loop body look more like an error case. 3. Use separate error variable name in loop body, to be clear we are not trying to influence the final return result. Fixes #6656. Fixes #6680. R=golang-dev, bradfitz CC=golang-dev https://golang.org/cl/18870043
-