forked from riscv/riscv-v-spec
-
Notifications
You must be signed in to change notification settings - Fork 0
/
20200320-V-minutes.txt
67 lines (48 loc) · 2.36 KB
/
20200320-V-minutes.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
Date: 2020/3/20
Task Group: Vector Extension
Chair: Krste Asanovic
Number of Attendees: ~20
Current issues on github: https://github.com/riscv/riscv-v-spec
Issues discussed: #367, #393
The following issues were discussed.
#367 Tail Agnostic
Proposal to add option of tail and/or mask agnostic behavior.
Concern about software incompatibility if agnostic option would allow
software to make use of 0s when this is detected. Proposal that
agnostic would require that either ones are written to non active
results, or they are left undisturbed. Writing ones is consistent
with scalar FP NaN-boxing.
It was noted that hardware could add a debugging mode that detected
when non-portable behavior was detected (using values written as
agnostic), but this would not be mandated.
To support thread migration between different microarchitectures
(e.g., big and little cores), it would be explicitly stated that
agnostic behavior (undisturbed versus writing ones) could change on
each execution of an instruction, or even when restarting an
instruction at non-zero vstart.
The tail and/or mask agnostic behavior would be recorded in vtype (or
maybe vcsr?)as two bits. Suggested encoding:
[1:0]
0 0 Tail undisturbed, masked undisturbed
1 0 Tail agnostic, masked undisturbed
1 1 Tail agnostic, masked agnostic
0 1 Illegal, sets vill
Implementations would be required to implement both state bits even if
the microarchitecture ignored setting and executed all options as
tail+mask undisturbed (a legal implementation).
Discussion to continue on mailing list.
#393 Fractional LMUL additional registers
Proposal to add fractional LMUL to support a greater number of usable
architecture registers in presence of mixed-width operands.
There was discussion about the new proposal on mapping fractional LMUL
elements when systems have SLEN<VLEN, as it appeared to break SLEN
wiring optimization. A scheme that appears to address the datapath
wiring concern spreads out fractional LMUL elements along the register
was discussed in meeting
VLEN=128b, SLEN=64b
F E D C B A 9 8 7 6 5 4 3 2 1 0 Byte number
X X X X X X X X X X X X 0 0 0 0 LMUL=1/4, SEW=32b
X X X X X X X X 0 0 0 0 0 0 0 0 LMUL=1/2, SEW=64b
X X X X 1 1 1 1 X X X X 0 0 0 0 LMUL=1/2, SEW=32b
1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 LMUL=1, SEW=64b
Discussion to continue on mailing list.