Thu Jul 14 16:55:28 SAT 2011

  ·	src/pkg/runtime/goc2c.c
	Check the return status from putchar() - removes the warnings
	and may even make some sort of diagnostic sense.

  ·	src/cmd/ld/lib.c
	Command line option to restore Plan 9 behaviour where only the
	necessary modules are loaded, not the entire library (check
	with Go Authors that this is a meaningful improvement).

  ·	src/cmd/mk*
	Make sure these mkfiles are consistent with building Go.
	Also, I think targets should be $O.$NAME rather than just
	$NAME (current Go preference) or $O.out (Plan 9 convention).
	But there may be factors I have not been taking into account.

  ·	src/pkg/runtime
	Build using freshly-constructed tools.  Needs mkfile.

  ·	src/cmd/[56]acl
	Bring other architectures in line with "386".

  ·	src/cmd/8c and src/cmd/gc
	This is the starting point for the Go compilers.  Its code was
	not written to the Plan 9 standards, so changes may be
	extensive (I know that Erik Quanstrom did compile 8g under
	Plan 9, so at least the scope is finite).  Conventions have
	been established on porting Go release code to Plan 9, which
	helps in the more recalcitrant cases.  These conventions need
	to be documented.

Fri Jul 15 16:07:51 SAT 2011

  ·	Plan 9 /bin/file to recognise Go executables and intermediates.

  ·	/go/src needs to be regularly manufactured from the CVS
	repository using selective "export" commands (there are a good
	few portions of the repository that are kept only for
	consistency - here teaching CVS to understand "proto" would be
	a treat).  Unfortunately, there is a synchronisation problem
	here, namely that there are portion of /go that are outside
	the "scope" of the CVS repository and yet require revision
	management.

  ·	Tidy up all mkfiles according to a yet-to-be-defined philosophy.

  ·	Add a "build" script to perform a number of actions:
	  ·	Export an abbreviated version of the Go release from the CVS
		repository, using partial "export" commands.
	  ·	Use the "proto" facility to extract the essential details not
		in the repository (effectively, not - yet - in the Go release)
		from an as yet unidentified source.

Fri Jul 29 13:29:18 SAT 2011

  .	Make sure that all mkfiles are consistent, as much as possible
	within the entire release, specially across architectures and
	platforms.  Also, whereas "mk install" works from src/cmd,
	just "mk" doesn't.

  .	A top-level mkfile in "/go" must include the target that
	reconstructs as many portions of the tree as is available
	under CVS, preferably everything.

  .	There are possible mk conflicts in building, typically,
	asm.$O, where there are different optional instances in
	different architecture directories.  These conflicts must be
	eliminated.
