Re: Vector Task Group minutes 2020/12/04
Alex Solomatnikov
One option is to allow mask generating instructions (compares) to write either to regular vector regs or to vmask and to provide move instructions between vector regs and vmask. But mask consuming instructions can use only vmask as a mask. Mask load and store are also only for vmask. This is no worse than current design. Alex
On Wed, Dec 16, 2020 at 12:29 PM Bill Huffman <huffman@...> wrote: I don’t think a separate mask register will do at all. It would take a mask register file with at least 8 and maybe 16 registers. Lots of compare results need to be kept and operations need to be done on mask registers. I don't think we should have a separate mask register file.
|
|