diff options
| author | Russ Cox <rsc@golang.org> | 2013-09-10 14:53:41 -0400 |
|---|---|---|
| committer | Russ Cox <rsc@golang.org> | 2013-09-10 14:53:41 -0400 |
| commit | 80a153dd5189d8bbc9d090f0ef0691c224d8b0a1 (patch) | |
| tree | 96a0345786f08c08704ea5cdc212ae211221ac1b /src/cmd/api | |
| parent | 8edf764fa3e2f760757d881d0e7e5eb80649bccb (diff) | |
| download | go-80a153dd5189d8bbc9d090f0ef0691c224d8b0a1.tar.xz | |
cmd/6l, cmd/8l: fix MOVL MOVQ optab
The entry for LEAL/LEAQ in these optabs was listed as having
two data bytes in the y array. In fact they had and expect no data
bytes. However, the general loop expects to be able to look at at
least one data byte, to make sure it is not 0x0f. So give them each
a single data byte set to 0 (not 0x0f).
Since the MOV instructions have the largest optab cases, this
requires growing the size of the data array.
Clang found this bug because the general o->op[z] == 0x0f
test was using z == 22, which was out of bounds.
In practice the next byte in memory was probably not 0x0f
so it wasn't truly broken. But might as well be clean.
Update #5764
R=ken2
CC=golang-dev
https://golang.org/cl/13241050
Diffstat (limited to 'src/cmd/api')
0 files changed, 0 insertions, 0 deletions