R=r
CC=golang-dev
https://golang.org/cl/2683041

Sub-symbols are laid out inside a larger symbol
but can be addressed directly.

Use to make Mach-O pointer array not a special case.

Will use later to describe ELF sections.

Glimpses of the beginning of ELF loading.

R=ken2
CC=golang-dev
https://golang.org/cl/2623043

The implemetation describes each value as a string identifying the
concrete type of the value, followed by the usual encoding of that
value.  All types to be exchanged as contents of interface values
must be registered ahead of time with the new Register function.
Although this would not seem strictly necessary, the linker garbage
collects unused types so without some mechanism to guarantee
the type exists in the binary, there could be unpleasant surprises.
Moreover, the receiver needs a reflect.Type of the value to be
written in order to be able to save the data. A Register function
seems necessary.

The implementation may require defining types in the middle of
of sending a value.  The old code never did this. Therefore there
has been some refactoring to make the encoder and decoder
work recursively.

This change changes the internal type IDs. Existing gob archives
will break with this change.  Apologies for that. If this is a deal
breaker it should be possible to create a conversion tool.

Error handling is too complicated in this code. A subsequent
change should clean it up.

R=rsc
CC=golang-dev
https://golang.org/cl/2618042

R=r, rsc
CC=golang-dev
https://golang.org/cl/2662041

gofmt: added -s flag to simplify composite literal expressions through type elision where possible

R=rsc
CC=golang-dev
https://golang.org/cl/2319041

For elements which are themselves composite literals, the type may
be omitted if it is identical to the element type of the containing
composite literal.

R=r, rsc, iant, ken2
CC=golang-dev
https://golang.org/cl/2661041

R=ken2
CC=golang-dev
https://golang.org/cl/2666041

R=ken2
CC=golang-dev
https://golang.org/cl/2658042

R=ken2
CC=golang-dev
https://golang.org/cl/2350041

by a variable that equals 32

R=rsc
CC=golang-dev
https://golang.org/cl/2645042

R=r, r2
CC=golang-dev
https://golang.org/cl/2663041

R=rsc
CC=golang-dev
https://golang.org/cl/2654041

R=ken2
CC=golang-dev
https://golang.org/cl/2650041

R=ken2
CC=golang-dev
https://golang.org/cl/2649041

R=ken2
CC=golang-dev
https://golang.org/cl/2621042

Fixes #1170.

R=rsc
CC=golang-dev
https://golang.org/cl/2622041

Load the entire archive file instead.
Reduces I/O by avoiding additional passes
through libraries to resolve symbols.
Go packages always need all the files anyway
(most often, all 1 of them).

R=ken2
CC=golang-dev
https://golang.org/cl/2613042

Giving them specific types has the benefit that
binary.BigEndian.Uint32(b) is now a direct call, not an
indirect via a mutable interface value, so it can potentially
be inlined.

Recent changes to the spec relaxed the rules for comparison,
so this code is still valid:

	func isLittle(o binary.ByteOrder) { return o == binary.LittleEndian }

The change does break this potential idiom:

	o := binary.BigEndian
	if foo {
		o = binary.LittleEndian
	}

That must rewrite to give o an explicit binary.ByteOrder type.
On balance I think the benefit from the direct call and inlining
outweigh the cost of breaking that idiom.

R=r, r2
CC=golang-dev
https://golang.org/cl/2427042

R=rsc
CC=golang-dev
https://golang.org/cl/2639041

Just enough to make mov instructions work,
which in turn is enough to make strconv work
when it avoids any floating point calculations.
That makes a bunch of other packages pass
their tests.

Should suffice until hardware floating point
is available.

Enable package tests that now pass
(some due to earlier fixes).

Looks like there is a new integer math bug
exposed in the fmt and json tests.

R=ken2
CC=golang-dev
https://golang.org/cl/2638041

(Hopefully this changeset will notice my +x to googlecode_upload.py)

Fixes #1217.

R=rsc
CC=golang-dev
https://golang.org/cl/2634041

R=rsc
CC=golang-dev
https://golang.org/cl/2637041

Fixes #1211.

R=r, r2
CC=golang-dev
https://golang.org/cl/2635041

Fixes #1145.

R=rsc
CC=golang-dev
https://golang.org/cl/2302042

R=golang-dev, adg
CC=golang-dev
https://golang.org/cl/2631041

R=r
CC=golang-dev
https://golang.org/cl/2624042

R=r, rsc
CC=golang-dev
https://golang.org/cl/2629041

R=golang-dev, adg
CC=golang-dev
https://golang.org/cl/2585043

gobuilder: fix build to work with new log package

R=rsc
CC=golang-dev
https://golang.org/cl/2592041

R=rsc, brainman
CC=golang-dev
https://golang.org/cl/2598041

An ARM expert could probably phrase the
comparison in fewer instructions, but this works.

R=ken2
CC=golang-dev
https://golang.org/cl/2620041

Thanks to avadh4all for spotting it.

Fixes #1214.

R=r, r2
CC=golang-dev
https://golang.org/cl/2616041

Fixes #1172.

R=ken2
CC=golang-dev
https://golang.org/cl/2615041

includes array[i]++ and slice[i]++

R=rsc
CC=golang-dev
https://golang.org/cl/2614041

Fixes #1209.

R=ken2
CC=golang-dev
https://golang.org/cl/2612041

R=kaib
CC=golang-dev
https://golang.org/cl/2608041

The frame that gets allocated is for both
the args and the autos.  If together they
exceed the default frame size, we need to
tell morestack about both so that it allocates
a large enough frame.

Sanity check stack pointer in morestack
to catch similar bugs.

R=ken2
CC=golang-dev
https://golang.org/cl/2609041

R=ken2
CC=golang-dev
https://golang.org/cl/2606041

Thanks to kaib for the tip.

R=ken2
CC=golang-dev
https://golang.org/cl/2596043

R=ken2
CC=golang-dev
https://golang.org/cl/2566042