aboutsummaryrefslogtreecommitdiff
path: root/build
diff options
context:
space:
mode:
authorAndrew Waterman <andrew@sifive.com>2021-10-05 19:15:45 -0700
committerAndrew Waterman <andrew@sifive.com>2021-10-05 19:15:45 -0700
commit399c9a759eb4540a65c60e2cc236164821ff2346 (patch)
tree48c25a05998554cf657d251251d91ea41d99461c /build
parent22c8813c7a05bd9d54892995b43e95f25f9df883 (diff)
downloadriscv-isa-manual-399c9a759eb4540a65c60e2cc236164821ff2346.zip
riscv-isa-manual-399c9a759eb4540a65c60e2cc236164821ff2346.tar.gz
riscv-isa-manual-399c9a759eb4540a65c60e2cc236164821ff2346.tar.bz2
Fix editing error in mtval/stval definition
Partially introduced by 7f45777bfc3e0a6b327552a286392ccfd5c933a8 and 94ab414c4b470edae8bde4e7759163fe7ddf8ab4 The spec says that the platform will define which exceptions must populate mtval or stval with a nonzero value and which are permitted to zero it. But then later statements seem not to permit the possibility of zeroing the register, which is a contradiction. Resolve in a backwards-compatible manner by permitting zeros unless the platform says otherwise (which was the original intent, anyway). This permits e.g. zeroing mtval on an EBREAK instruction, where mepc provides sufficient information, as was the intent of 94ab414c4b470edae8bde4e7759163fe7ddf8ab4.
Diffstat (limited to 'build')
0 files changed, 0 insertions, 0 deletions