On Thu, 1 Jun 2023 at 18:49, Jeff Law via Gcc-patches <gcc-patches@gcc.gnu.org> wrote: > > > > On 6/1/23 01:01, juzhe.zh...@rivai.ai wrote: > > I plan to implement BF16 vector in GCC but still waiting for ISA > > ratified since GCC policy doesn't allow un-ratified ISA. > Right. So those specs need to move along further before we can start > integrating code.
Doesn't our policy require specs to only pass the FREEZE milestone (i.e., the requirement for public review) before we can start integrating them? This should give us at least a 6 week (minimum 30 days public-review plus 2 weeks for the TSC vote to send this up for ratification) headstart on ratification (with the small risk of minor changes required due to review comments) to start integrating support for new extensions. Best, Philipp. p.s.: Just for reference, the RISC-V Lifecycle Guide (defining these milestones in specification development) is linked from https://wiki.riscv.org/ for details. > > > > Currently, we are working on INT8,INT16,INT32,INT64,FP16,FP32,FP64 > > auto-vectorizaiton. > > It should very simple BF16 in current vector framework in GCC. > In prior architectures I've worked on the bulk of BF16 work was just > adding additional entries to existing iterators. So I agree, it should > be very simple :-) > > Jeff >
