From 0480371cb947bc54e9a0d9c5653a76a4f614654d Mon Sep 17 00:00:00 2001 From: Luke Kenneth Casson Leighton Date: Wed, 17 Oct 2018 12:46:50 +0100 Subject: [PATCH] add tag --- simple_v_extension/specification.mdwn | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/simple_v_extension/specification.mdwn b/simple_v_extension/specification.mdwn index c59f84f6d..4ea6f6d9c 100644 --- a/simple_v_extension/specification.mdwn +++ b/simple_v_extension/specification.mdwn @@ -1140,9 +1140,9 @@ during the hardware loop, **not** the offset. Element bitwidth is best covered as its own special section, as it is quite involved and applies uniformly across-the-board. -The effect of setting an element bitwidth is to re-cast the register -table to a completely different width. In c-style terms, on an -RV64 architecture, effectively each register looks like this: +The effect of setting an element bitwidth is to re-cast each entry +in the register table to a completely different width. In c-style terms, +on an RV64 architecture, effectively each register looks like this: typedef union { uint8_t b[8]; @@ -1160,7 +1160,7 @@ to the following parts of the register file in a sequential fashion. So a much more accurate way to reflect this would be: typedef union { - uint8_t actual_register_bytes[8]; + uint8_t actual_bytes[8]; // 8 for RV64, 4 for RV32, 16 for RV128 uint8_t *b; uint16_t *s; uint32_t *i; -- 2.30.2