|
Re: Issue categorization - #460
Forgive top posting, but the email was long and I want to bring key
points forward for others.
#458/460 propose restricting allowed register numbers in a vsetvli to
give more bits to future vsetvli
Forgive top posting, but the email was long and I want to bring key
points forward for others.
#458/460 propose restricting allowed register numbers in a vsetvli to
give more bits to future vsetvli
|
By
Krste Asanovic
·
#244
·
|
|
Re: Issue categorization - #460
I think I understand how I confused the situation.
Issue #458 introduced idea of using rd and rs1 values to encode more bits for vsetvli.
I proposed that this become the only vsetvli format.
Krste
I think I understand how I confused the situation.
Issue #458 introduced idea of using rd and rs1 values to encode more bits for vsetvli.
I proposed that this become the only vsetvli format.
Krste
|
By
David Horner
·
#243
·
|
|
Re: Duplicate Counting Instruction
tech-vector-ext got dropped somehow, adding again.
We have to keep technical discussion on tech-vector-ext public mailing list.
| On Jun 30, 2020, at 12:35 AM, Roger Espasa
tech-vector-ext got dropped somehow, adding again.
We have to keep technical discussion on tech-vector-ext public mailing list.
| On Jun 30, 2020, at 12:35 AM, Roger Espasa
|
By
Krste Asanovic
·
#242
·
|
|
Re: Issue categorization - #460
For 1.0, we are just trying to fix vsew, vlmul, vma, and vta (and also vill in vtype, but that’s out of vsetvli immediate range).
I think it’s clear that vma and vta are not going to change very
For 1.0, we are just trying to fix vsew, vlmul, vma, and vta (and also vill in vtype, but that’s out of vsetvli immediate range).
I think it’s clear that vma and vta are not going to change very
|
By
Krste Asanovic
·
#241
·
|
|
Re: Issue categorization - #460
On 2020-06-29 10:36 a.m., Krste Asanovic wrote:
It is a planned extension, that even if not implemented as currently proposed it will likely consume at least 2 bits in vtype.
On 2020-06-29 10:36 a.m., Krste Asanovic wrote:
It is a planned extension, that even if not implemented as currently proposed it will likely consume at least 2 bits in vtype.
|
By
David Horner
·
#240
·
|
|
Re: Issue categorization - #460
Can you focus on what would not be possible if we ratified current proposal.
Remember EDIV is not in 1.0 and Vlmul=100 is reserved
Krste
Can you focus on what would not be possible if we ratified current proposal.
Remember EDIV is not in 1.0 and Vlmul=100 is reserved
Krste
|
By
Krste Asanovic
·
#239
·
|
|
Re: Issue categorization - #460
minor typos; substantial correction:
On 2020-06-29 10:12 a.m., David Horner via lists.riscv.org wrote:
also throughout the email
vd should be rd
vs1 should be
minor typos; substantial correction:
On 2020-06-29 10:12 a.m., David Horner via lists.riscv.org wrote:
also throughout the email
vd should be rd
vs1 should be
|
By
David Horner
·
#238
·
|
|
Re: Issue categorization - #460
I disagree that #460 should be deferred until after V1.0.
Although I agree that the proposal itself can be implemented in a manner consistent with the current vsetvli definition,
I
I disagree that #460 should be deferred until after V1.0.
Although I agree that the proposal itself can be implemented in a manner consistent with the current vsetvli definition,
I
|
By
David Horner
·
#237
·
|
|
Re: Issue categorization - object to closing #478
I don't agree that #478 should be closed for the reasons given.
I do agree that another approach might be better to superseded that which was originally proposed.
But I do not agree with the proposed
I don't agree that #478 should be closed for the reasons given.
I do agree that another approach might be better to superseded that which was originally proposed.
But I do not agree with the proposed
|
By
David Horner
·
#236
·
|
|
Issue categorization
I made a pass over the spec repo, adding red labels for “resolve for v1.0’ , versus yellow labels for "resolve after v1.0”.
I also cleaned up and closed some other issues.
"Resolve after’
I made a pass over the spec repo, adding red labels for “resolve for v1.0’ , versus yellow labels for "resolve after v1.0”.
I also cleaned up and closed some other issues.
"Resolve after’
|
By
Krste Asanovic
·
#235
·
|
|
RISC-V Vector Extension TG Minutes 2020/6/26
Date: 2020/6/26
Task Group: Vector Extension
Chair: Krste Asanovic
Co-Chair: Roger Espasa
Number of Attendees: ~15
Current issues on github: https://github.com/riscv/riscv-v-spec
Thanks to all the
Date: 2020/6/26
Task Group: Vector Extension
Chair: Krste Asanovic
Co-Chair: Roger Espasa
Number of Attendees: ~15
Current issues on github: https://github.com/riscv/riscv-v-spec
Thanks to all the
|
By
Krste Asanovic
·
#234
·
|
|
Re: Vector Wins
The warehouse is the computer. Modern cloud companies have warehouses that hold 50,000 severs at 30-60 MegaWatts for air cooled or water cooled clusters
Dave
The warehouse is the computer. Modern cloud companies have warehouses that hold 50,000 severs at 30-60 MegaWatts for air cooled or water cooled clusters
Dave
|
By
Dave Patterson
·
#233
·
|
|
Re: Vector Wins
How do you cool a 28MW computer?
On Thu, 2020-06-25 at 14:28 -0700, David Patterson via lists.riscv.org wrote:
--
Derek Atkins
Chief Technology Officer
Veridify Security - Securing the Internet of
How do you cool a 28MW computer?
On Thu, 2020-06-25 at 14:28 -0700, David Patterson via lists.riscv.org wrote:
--
Derek Atkins
Chief Technology Officer
Veridify Security - Securing the Internet of
|
By
Derek Atkins <datkins@...>
·
#232
·
|
|
Next Vector TG Meeting Friday June 26
We’ll be meeting later today per the member calendar,
Krste
We’ll be meeting later today per the member calendar,
Krste
|
By
Krste Asanovic
·
#231
·
|
|
Vector Wins
In case you missed it, yesterday the HPC community announced the "world's fastest computer" (based on Linpack) is based on the Fujitsu A64FX, which is the first to implement the ARM Scalable Vector
In case you missed it, yesterday the HPC community announced the "world's fastest computer" (based on Linpack) is based on the Fujitsu A64FX, which is the first to implement the ARM Scalable Vector
|
By
David Patterson <pattrsn@...>
·
#230
·
|
|
Re: On Vector Register Layout
The wide register being the destination, correct?
Not sure I follow this, which two registers? If physical registers, then no.
That design was the v0.8 method of vertical cycling through physical
The wide register being the destination, correct?
Not sure I follow this, which two registers? If physical registers, then no.
That design was the v0.8 method of vertical cycling through physical
|
By
David Horner
·
#229
·
|
|
Re: On Vector Register Layout
Hi David,
If I try to compare this to the current proposal, it seems to me there
are two major differences.
** A layout difference in the wide registers where elements alternate
between two
Hi David,
If I try to compare this to the current proposal, it seems to me there
are two major differences.
** A layout difference in the wide registers where elements alternate
between two
|
By
Bill Huffman
·
#228
·
|
|
Re: On Vector Register Layout
I will make a stab at even and odd layout for widening.
5) two versions of the widening ops are defined one for even and one odd.
The registers are divided into even:odd pairs.
Two versions of the
I will make a stab at even and odd layout for widening.
5) two versions of the widening ops are defined one for even and one odd.
The registers are divided into even:odd pairs.
Two versions of the
|
By
David Horner
·
#227
·
|
|
VFRECIP/VFRSQRT instructions
The task group has recommended moving forward with adding instructions that estimate reciprocals and reciprocal square roots. These are both useful for -ffast-math code where it's acceptable to
The task group has recommended moving forward with adding instructions that estimate reciprocals and reciprocal square roots. These are both useful for -ffast-math code where it's acceptable to
|
By
Andrew Waterman
·
#226
·
|
|
Re: Whole Register Loads and Stores
| Hi
Hi Kito,
|| 3) Spill code inside loop
||
|| This is the most problematic case. I wonder about how often the
|| compiler does not know the type and length of the values to be
|| restored? I
| Hi
Hi Kito,
|| 3) Spill code inside loop
||
|| This is the most problematic case. I wonder about how often the
|| compiler does not know the type and length of the values to be
|| restored? I
|
By
Krste Asanovic
·
#225
·
|