diff options
| author | Austin Clements <austin@google.com> | 2014-10-31 11:08:27 -0400 |
|---|---|---|
| committer | Austin Clements <austin@google.com> | 2014-10-31 11:08:27 -0400 |
| commit | bfab3e583ce8e78b9488fdb292f3f371949757a6 (patch) | |
| tree | c7190580bc2a0dcef4a4a03a21604ceffcac8b19 /src/runtime/asm_power64x.s | |
| parent | 905f3e7cf489f05ae3764cabda3cd96684e3445f (diff) | |
| download | go-bfab3e583ce8e78b9488fdb292f3f371949757a6.tar.gz | |
[dev.power64] 9g: fix under-zeroing in clearfat
All three cases of clearfat were wrong on power64x.
The cases that handle 1032 bytes and up and 32 bytes and up
both use MOVDU (one directly generated in a loop and the other
via duffzero), which leaves the pointer register pointing at
the *last written* address. The generated code was not
accounting for this, so the byte fill loop was re-zeroing the
last zeroed dword, rather than the bytes following the last
zeroed dword. Fix this by simply adding an additional 8 byte
offset to the byte zeroing loop.
The case that handled under 32 bytes was also wrong. It
didn't update the pointer register at all, so the byte zeroing
loop was simply re-zeroing the beginning of region. Again,
the fix is to add an offset to the byte zeroing loop to
account for this.
LGTM=dave, bradfitz
R=rsc, dave, bradfitz
CC=golang-codereviews
https://codereview.appspot.com/168870043
Diffstat (limited to 'src/runtime/asm_power64x.s')
| -rw-r--r-- | src/runtime/asm_power64x.s | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/runtime/asm_power64x.s b/src/runtime/asm_power64x.s index ab2db061c..2ad3e56e9 100644 --- a/src/runtime/asm_power64x.s +++ b/src/runtime/asm_power64x.s @@ -829,7 +829,7 @@ notfound: // in ../../cmd/9g/ggen.c:/^clearfat. // R0: always zero // R3 (aka REGRT1): ptr to memory to be zeroed - 8 -// R3 is updated as a side effect. +// On return, R3 points to the last zeroed dword. TEXT runtime·duffzero(SB), NOSPLIT, $-8-0 MOVDU R0, 8(R3) MOVDU R0, 8(R3) |