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

value (through unsafe means) without having a reflect.Type
of type *interface{} (pointer to interface).  This is needed to make
gob able to handle interface values by a method analogous to
the way it handles maps.

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

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

Fixes #671.

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

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

R=brainman, vcc, Joe Poirier, rsc
CC=golang-dev
https://golang.org/cl/2530041

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

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

That is, move the pc/ln table and the symbol table
into the read-only data segment.  This eliminates
the need for a special load command to map the
symbol table into memory, which makes the
information available on systems that couldn't handle
the magic load to 0x99000000, like NaCl and ARM QEMU
and Linux without config_highmem=y.  It also
eliminates an #ifdef and some clumsy code to
find the symbol table on Windows.

The bad news is that the binary appears to be bigger
than it used to be.  This is not actually the case, though:
the same amount of data is being mapped into memory
as before, and the tables are still read-only, so they're
still shared across multiple instances of the binary as
they were before.  The difference is just that the tables
aren't squirreled away in some section that "size" doesn't
know to look at.

This is a checkpoint.
It probably breaks Windows and breaks NaCl more
than it used to be broken, but those will be fixed.
The logic involving -s needs to be revisited too.

Fixes #871.

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

Lay out code before data.

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