ARM functionality is now completely working.
(Or if it's not, we'll fix it.)

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

Fixes #1158.

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

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

Adds softfloat64 to generic runtime
(will be discarded by linker when unused)
and adds test for it.  I used the test to check
the software code against amd64 hardware
and then check the software code against
the arm and its simulation of hardware.
The latter should have been a no-op (testing
against itself) but turned up a bug in 5c causing
the vlrt.c routines to miscompile.

These changes make the cmath, math,
and strconv tests pass without any special
accommodations for arm.

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

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

R=rsc, r2
CC=golang-dev
https://golang.org/cl/2733041

R=rsc, r2
CC=golang-dev
https://golang.org/cl/2735041

Fixes #1225.

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

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

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

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

         (language change as discussed a while ago)

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

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

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

There are other missing conversion cases
still but they do not show up in my tests.
This one is needed for vlrt.c's _v2d (int64, uint64 -> float).

Thankfully, VFP has a single instruction to do this.

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

Fixes #1223.

R=bradfitz
CC=golang-dev
https://golang.org/cl/2701041

R=dsymonds
CC=golang-dev
https://golang.org/cl/2700041

Remove wasn't nil'ing the *Element.id. This property was exploited
by MoveToFront and MoveToBack internally, so I renamed the existing
Remove to "remove", and created an exported wrapper "Remove" that does
the right thing for the user's sake.

Also, saved an allocation by using *List as the id rather than *byte.

Fixes #1224.

R=rsc, dsymonds
CC=golang-dev
https://golang.org/cl/2685042

Fixes #1215.

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

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

Simplify error handling during the compilation phase.

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

Remove err from the encoderState and decoderState types, so we're
not always copying to and from various copies of the error, and then
use panic/recover to eliminate lots of error checking.

another pass might take a crack at the same thing for the compilation phase.

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

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