Do sign-extension instructions in writeback instead of execute1
authorPaul Mackerras <paulus@ozlabs.org>
Mon, 14 Oct 2019 03:39:23 +0000 (14:39 +1100)
committerPaul Mackerras <paulus@ozlabs.org>
Tue, 15 Oct 2019 04:27:00 +0000 (15:27 +1100)
commit9646fe28b089c7f03aeef5d3d32a590652732ec2
treeebb931cf55f29deea63270d3e1968e290a6d9659
parent374f4c536d3c4dd8051a139b8e25691ba82e35b7
Do sign-extension instructions in writeback instead of execute1

This makes the exts[bhw] instructions do the sign extension in the
writeback stage using the sign-extension logic there instead of
having unique sign extension logic in execute1.  This requires
passing the data length and sign extend flag from decode2 down
through execute1 and execute2 and into writeback.  As a side bonus
we reduce the number of values in insn_type_t by two.

Signed-off-by: Paul Mackerras <paulus@ozlabs.org>
common.vhdl
decode1.vhdl
decode2.vhdl
decode_types.vhdl
execute1.vhdl
execute2.vhdl
writeback.vhdl