public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: jiawei@iscas.ac.cn
To: gcc@gcc.gnu.org, binutils@sourceware.org, gdb@sourceware.org,
	 libc-alpha@sourceware.org
Cc: christoph.muellner@vrull.eu, jeremy.bennett@embecosm.com,
	 jim.wilson.gcc@gmail.com, kito.cheng@sifive.com,
	 nelson.chu@sifive.com, palmer@dabbelt.com,
	philipp.tomsich@vrull.eu,  wuwei2016@iscas.ac.cn,
	shihua@iscas.ac.cn, sinan@isrc.iscas.ac.cn,
	 yulong@nj.iscas.ac.cn
Subject: [RISCV] RISC-V GNU Toolchain Meeting Cancell (May 19, 2022)
Date: Wed, 18 May 2022 22:29:59 +0800 (GMT+08:00)	[thread overview]
Message-ID: <7784cc2b.53d86.180d793592f.Coremail.jiawei@iscas.ac.cn> (raw)

Hi all,



    Tomorrow meeting will cancel since there are few new topics to discuss.  




    FYI,  




    Kito had bumped current RVV toolchain support into a rvv-next branch on riscv-gnu-toolchain repo,

 https://github.com/riscv-collab/riscv-gnu-toolchain/tree/rvv-next




 Zhong Juzhe had finish RVV tests with tensorflow project, now it can pass all tensorflow operator with auto-vectoraztion,

    remove -mrvv option and fixed bugs tested on dejagnu. Remain some arithmetic questions: https://github.com/riscv-collab/riscv-gnu-toolchain/issues/1075




    Pamler handle a riscv-gnu-toolchain submodule shift PR and make some disscuss: https://github.com/riscv-collab/riscv-gnu-toolchain/pull/1074

   


   FP16 support discuss: https://github.com/riscv-collab/riscv-gnu-toolchain/issues/1077




Regrads,

PLCT Jiawei

                 reply	other threads:[~2022-05-18 14:30 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7784cc2b.53d86.180d793592f.Coremail.jiawei@iscas.ac.cn \
    --to=jiawei@iscas.ac.cn \
    --cc=binutils@sourceware.org \
    --cc=christoph.muellner@vrull.eu \
    --cc=gcc@gcc.gnu.org \
    --cc=gdb@sourceware.org \
    --cc=jeremy.bennett@embecosm.com \
    --cc=jim.wilson.gcc@gmail.com \
    --cc=kito.cheng@sifive.com \
    --cc=libc-alpha@sourceware.org \
    --cc=nelson.chu@sifive.com \
    --cc=palmer@dabbelt.com \
    --cc=philipp.tomsich@vrull.eu \
    --cc=shihua@iscas.ac.cn \
    --cc=sinan@isrc.iscas.ac.cn \
    --cc=wuwei2016@iscas.ac.cn \
    --cc=yulong@nj.iscas.ac.cn \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).