[dev.power64] code review 128350043: cmd/9g: fix final fragment in clearfat

cmd/9g: fix final fragment in clearfat

Was re-clearing the beginning of the block
instead of end.

There may still be a bug in that clearfat
assumes unaligned writes are okay.
I don't know whether they are.

[rsc, 2014-08-15 21:20:26]

Hello minux (cc: golang-codereviews@googlegroups.com),

I'd like you to review this change to the dev.power64 branch of
https://code.google.com/p/go/

[minux, 2014-08-15 23:02:37]

Thanks Russ.
FTR, This fixes the little-endian image/jpeg and image test failures.

I will double check clearfat.
Unaligned access is allowed, but might be slow.

[rsc, 2014-08-15 23:03:01]

it might be that we always 8-align things 8 bytes or larger on the stack.

[minux, 2014-08-19 02:29:22]

On 2014/08/15 23:03:01, rsc wrote:
> it might be that we always 8-align things 8 bytes or larger on the stack.
Yes. I think so.

[minux, 2014-08-19 02:36:45]

This CL contains two independent bug fixes.
Please update the description.

cmd/9g: fix setting saved LR for deferproc/newproc, and the final fragment in
clearfat()

or, if you prefer, I can split them into two separate CLs.

[minux, 2014-08-19 04:42:37]

LGTM after updating the description.

[gobot, 2014-12-19 04:55:48]

R=close

To the author of this CL:

The Go project has moved to Gerrit Code Review.

If this CL should be continued, please see the latest version of
http://golang.org/doc/contribute.html for instructions on
how to set up Git and the Go project's Gerrit codereview plugin,
and then create a new change with your current code.

If there has been discussion on this CL, please give a link to it
(golang.org/cl/NNNNNNN is best) in the description in your
new CL.

Thanks very much.

[gobot, 2014-12-19 04:56:53]

R=close

To the author of this CL:

The Go project has moved to Gerrit Code Review.

If this CL should be continued, please see the latest version of
http://golang.org/doc/contribute.html for instructions on
how to set up Git and the Go project's Gerrit codereview plugin,
and then create a new change with your current code.

If there has been discussion on this CL, please give a link to it
(golang.org/cl/NNNNNNN is best) in the description in your
new CL.

Thanks very much.