
HalfPrecision, BFloat16, and Other Float Encoding: Reference Model Recommendations from Task Group
In support of Open Source Software and publicly released modeling schemes, does the Vector Task Group have a recommendation for arithmetic reference? The published ISSs can provide checking results fr
In support of Open Source Software and publicly released modeling schemes, does the Vector Task Group have a recommendation for arithmetic reference? The published ISSs can provide checking results fr

By
CDS
· #514
·


Please check new Google calendar for new vector TG meeting link
It looks like there are two calendars – one on the riscv site, and one on google (someone else sent to me). And the ZOOM meeting invites are not the same between them :\ Cohen From: Nick Knight <nic
It looks like there are two calendars – one on the riscv site, and one on google (someone else sent to me). And the ZOOM meeting invites are not the same between them :\ Cohen From: Nick Knight <nic

By
CDS
· #431
·


Please check new Google calendar for new vector TG meeting link
Can you publish a link to what the Google Calendar is, or the TG meeting link? There are no links on this site to any of that information.
Can you publish a link to what the Google Calendar is, or the TG meeting link? There are no links on this site to any of that information.

By
CDS
· #429
·


Mask Register Value Mapping
Word of caution: there may be a utility/readability concern if the ".LSB" text is removed, only. This would create a phrase vs2[i] + vs1[i] + v0[i] which can easily be misleading to the reader  while
Word of caution: there may be a utility/readability concern if the ".LSB" text is removed, only. This would create a phrase vs2[i] + vs1[i] + v0[i] which can easily be misleading to the reader  while

By
CDS
· #424
·


Mask Register Value Mapping
Thank you Andrew and Nick. To avoid having to repeat this question later, is it the intent moving forward (beyond "this version of the spec" being 0.9 stable) that this will hold true in the same form
Thank you Andrew and Nick. To avoid having to repeat this question later, is it the intent moving forward (beyond "this version of the spec" being 0.9 stable) that this will hold true in the same form

By
CDS
· #422
·


Mask Register Value Mapping
From 0.9 stable spec, 5.3.1, table (no number), vector masking is referred to as having LSB. This suggests, yet does not require, that the mask field for each element is greater than bitsize 1. From
From 0.9 stable spec, 5.3.1, table (no number), vector masking is referred to as having LSB. This suggests, yet does not require, that the mask field for each element is greater than bitsize 1. From

By
CDS
· #419
·


Signed v Unsigned Immediate: vsaddu.vi
Andrew, Nick, Thank you for the quick responses. Nick, the text updates look like they directly reflect the intent. Cohen
Andrew, Nick, Thank you for the quick responses. Nick, the text updates look like they directly reflect the intent. Cohen

By
CDS
· #388
·


Signed v Unsigned Immediate: vsaddu.vi
From chapter 11, section 1 (#3): The 5bit immediate is unsigned when either providing a register index in vrgather or a count for shift, clip, or slide. In all other cases it is signed and sign exten
From chapter 11, section 1 (#3): The 5bit immediate is unsigned when either providing a register index in vrgather or a count for shift, clip, or slide. In all other cases it is signed and sign exten

By
CDS
· #380
·


Fixed Point (Chapter 13): Clarification Request
Nick, Thank you for your response and proposed clarification. This proposal for how to use the numbers fundamentally realigns our interpretation of how this would be used. This is much closer to the t
Nick, Thank you for your response and proposed clarification. This proposal for how to use the numbers fundamentally realigns our interpretation of how this would be used. This is much closer to the t

By
CDS
· #329
·


Integer Overflow/Saturation Operations
Andy, Thank you for your response. The concern I'm raising is less about "How do I avoid overflow?" and more about "Why are we avoiding the specification of saturating instructions, or an overflow fla
Andy, Thank you for your response. The concern I'm raising is less about "How do I avoid overflow?" and more about "Why are we avoiding the specification of saturating instructions, or an overflow fla

By
CDS
· #326
·


Fixed Point (Chapter 13): Clarification Request
Perhaps, it is important to understand the history of why fixed point is utilized. Historically, fixed point was the alternative for expensive floating point implementations/operations, or was the eas
Perhaps, it is important to understand the history of why fixed point is utilized. Historically, fixed point was the alternative for expensive floating point implementations/operations, or was the eas

By
CDS
· #325
·
Edited


Fixed Point (Chapter 13): Clarification Request
Thank you for the response, Andrew. Given that these operations are intended to be conveniences, in the first place (hence: vector), the addition of a required macro for inclusion could be considered
Thank you for the response, Andrew. Given that these operations are intended to be conveniences, in the first place (hence: vector), the addition of a required macro for inclusion could be considered

By
CDS
· #320
·


vrsub.vi, used as negation
Is the point of vrsub.vi to provide negation? From a compiler/user perspective, completing the vsub pattern with vsub.vi (even as a virtual instruction) may be a usability enhancement to consider.
Is the point of vrsub.vi to provide negation? From a compiler/user perspective, completing the vsub pattern with vsub.vi (even as a virtual instruction) may be a usability enhancement to consider.

By
CDS
· #317
·


Integer Overflow/Saturation Operations
Vectorwidening multiply & accumulate instructions: These instructions, signed or unsigned, will quickly overflow in even simple cases. Given absence of flagging (e.g. OVERFLOW), a saturating version
Vectorwidening multiply & accumulate instructions: These instructions, signed or unsigned, will quickly overflow in even simple cases. Given absence of flagging (e.g. OVERFLOW), a saturating version

By
CDS
· #316
·


Fixed Point (Chapter 13): Clarification Request
The definition of the numeric range (at the beginning of section 13) matches the definition of an integer, not of a fixedpoint number. For example, the range specified is the range of an integer, not
The definition of the numeric range (at the beginning of section 13) matches the definition of an integer, not of a fixedpoint number. For example, the range specified is the range of an integer, not

By
CDS
· #315
·
