go/test/golden.out


== ./

== ken/

== chan/

== interface/

== syntax/

== dwarf/

== safe/

== fixedbugs/

=========== fixedbugs/bug429.go
throw: all goroutines are asleep - deadlock!

== bugs/

=========== bugs/bug395.go
bug395 is broken

=========== bugs/bug434.go
bugs/bug434.dir/two.go:10: one.t.int undefined (cannot refer to unexported field or method one.int)
BUG:bug434
- fix to func.go - extra empty line between test output SVN=121499 2008-06-06 22:08:24 +00:00
tweak final line of test output: 4 known bugs; 0 unexpected bugs which should be less scary to people unfamiliar with the tests. R=r DELTA=44 (29 added, 12 deleted, 3 changed) OCL=32460 CL=32464 2009-07-29 22:11:19 +00:00			`== ./`

			`== ken/`

			`== chan/`

			`== interface/`

gc: improved syntax errors * example-based syntax errors (go.errors) * enable bison's more specific errors and translate grammar token names into tokens like ++ * test cases R=ken2, r, ken3 CC=golang-dev https://golang.org/cl/194085 2010-01-27 07:13:22 +00:00			`== syntax/`

ld: grow dwarf includestack on demand. Fixes #2241 while not breaking issue 1878 again. R=rsc CC=golang-dev https://golang.org/cl/4988048 2011-09-09 13:08:57 +00:00			`== dwarf/`

cmd/gc: suspend safemode during typecheck of inlined bodies. Should be obviously correct. Includes minimal test case. A future CL should clear up the logic around typecheckok and importpkg != nil someday. R=rsc, dsymonds, rsc CC=golang-dev https://golang.org/cl/5652057 2012-02-10 21:50:55 +00:00			`== safe/`

tweak final line of test output: 4 known bugs; 0 unexpected bugs which should be less scary to people unfamiliar with the tests. R=r DELTA=44 (29 added, 12 deleted, 3 changed) OCL=32460 CL=32464 2009-07-29 22:11:19 +00:00			`== fixedbugs/`
triple quote R=ken OCL=31868 CL=31874 2009-07-20 21:15:36 +00:00
runtime: work around false negative in deadlock detection Not a complete fix for issue 3342, but fixes the trivial case. There may still be a race in the instants before and after a scavenger-induced garbage collection. Intended to be "obviously safe": a call to runtime·gosched before main.main is no different than a call to runtime.Gosched at the beginning of main.main, and it is (or had better be) safe to call runtime.Gosched at any point during main. Update #3342. R=iant CC=golang-dev https://golang.org/cl/5919052 2012-03-27 16:22:19 +00:00			`=========== fixedbugs/bug429.go`
			`throw: all goroutines are asleep - deadlock!`

tweak final line of test output: 4 known bugs; 0 unexpected bugs which should be less scary to people unfamiliar with the tests. R=r DELTA=44 (29 added, 12 deleted, 3 changed) OCL=32460 CL=32464 2009-07-29 22:11:19 +00:00			`== bugs/`
gc: undo most of 'fix infinite recursion for embedded interfaces' Preserve test. changeset: 11593:f1deaf35e1d1 user: Luuk van Dijk <lvd@golang.org> date: Tue Jan 17 10:00:57 2012 +0100 summary: gc: fix infinite recursion for embedded interfaces This is causing 'interface type loop' errors during compilation of a complex program. I don't understand what's happening well enough to boil it down to a simple test case, but undoing this change fixes the problem. The change being undone is fixing a corner case (uses of pointer to interface in an interface definition) that basically only comes up in erroneous Go programs. Let's not try to fix this again until after Go 1. Unfixes issue 1909. TBR=lvd CC=golang-dev https://golang.org/cl/5555063 2012-01-20 22:14:09 +00:00
			`=========== bugs/bug395.go`
			`bug395 is broken`
cmd/gc: test for issue 3552 R=rsc CC=golang-dev https://golang.org/cl/6128051 2012-05-02 14:56:26 +00:00
			`=========== bugs/bug434.go`
			`bugs/bug434.dir/two.go:10: one.t.int undefined (cannot refer to unexported field or method one.int)`
			`BUG:bug434`