From: 陈逸轩 <chenyixuan@iscas.ac.cn>
To: "Kito Cheng" <kito.cheng@gmail.com>, "Robin Dapp" <rdapp.gcc@gmail.com>
Cc: gcc-patches@gcc.gnu.org, andrew@sifive.com,
shiyulong@iscas.ac.cn, oriachiuan@gmail.com, shihua@iscas.ac.cn,
jiawei@iscas.ac.cn
Subject: Re: Re: [PATCH] Add VXRM enum
Date: Thu, 13 Jul 2023 15:54:33 +0800 (GMT+08:00) [thread overview]
Message-ID: <50829a64.1ea0.1894e3e9b23.Coremail.chenyixuan@iscas.ac.cn> (raw)
In-Reply-To: <CA+yXCZCY3pMToVEBakQFJeUbtsXKc0Mrg3Zf3iAu-kSziG9n7A@mail.gmail.com>
Oh, sorry for that, thank you very much! XD
> -----Original Messages-----
> From: "Kito Cheng" <kito.cheng@gmail.com>
> Sent Time: 2023-07-13 15:24:45 (Thursday)
> To: "Robin Dapp" <rdapp.gcc@gmail.com>
> Cc: chenyixuan@iscas.ac.cn, gcc-patches@gcc.gnu.org, andrew@sifive.com, shiyulong@iscas.ac.cn, oriachiuan@gmail.com, shihua@iscas.ac.cn, jiawei@iscas.ac.cn
> Subject: Re: [PATCH] Add VXRM enum
>
> Those enum values have been defined via `#pragma riscv intrinsic "vector"` :)
>
> https://github.com/gcc-mirror/gcc/commit/01d62e9b6c3e9fd3132f1616843103ccf81778ed
>
> On Thu, Jul 13, 2023 at 2:55 PM Robin Dapp via Gcc-patches
> <gcc-patches@gcc.gnu.org> wrote:
> >
> > > +enum __RISCV_VXRM {
> > > + __RISCV_VXRM_RNU = 0,
> > > + __RISCV_VXRM_RNE = 1,
> > > + __RISCV_VXRM_RDN = 2,
> > > + __RISCV_VXRM_ROD = 3,
> > > +};
> > > +
> > > __extension__ extern __inline unsigned long
> > > __attribute__ ((__always_inline__, __gnu_inline__, __artificial__))
> > > vread_csr(enum RVV_CSR csr)
> >
> > We have that already in riscv-protos.h :)
> > (fixed_point_rounding_mode)
> >
> > Regards
> > Robin
> >
</gcc-patches@gcc.gnu.org></rdapp.gcc@gmail.com></kito.cheng@gmail.com>
prev parent reply other threads:[~2023-07-13 7:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-13 6:31 chenyixuan
2023-07-13 6:54 ` Robin Dapp
2023-07-13 7:24 ` Kito Cheng
2023-07-13 7:54 ` 陈逸轩 [this message]
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=50829a64.1ea0.1894e3e9b23.Coremail.chenyixuan@iscas.ac.cn \
--to=chenyixuan@iscas.ac.cn \
--cc=andrew@sifive.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jiawei@iscas.ac.cn \
--cc=kito.cheng@gmail.com \
--cc=oriachiuan@gmail.com \
--cc=rdapp.gcc@gmail.com \
--cc=shihua@iscas.ac.cn \
--cc=shiyulong@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).