From: Kito Cheng <kito.cheng@gmail.com>
To: Jeff Law <jeffreyalaw@gmail.com>
Cc: 钟居哲 <juzhe.zhong@rivai.ai>,
"GCC Patches" <gcc-patches@gcc.gnu.org>,
"Palmer Dabbelt" <palmer@dabbelt.com>
Subject: Re: [PATCH] RISC-V: Change vlmul printing rule
Date: Mon, 19 Dec 2022 23:07:49 +0800 [thread overview]
Message-ID: <CA+yXCZA_Uyrj6rAfRmZuH+yXJoJTRcrMwgdEhtQnedUc02MDSQ@mail.gmail.com> (raw)
In-Reply-To: <c3444d68-7a26-74e2-f388-195c91c07773@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 869 bytes --]
Commited
Jeff Law via Gcc-patches <gcc-patches@gcc.gnu.org> 於 2022年12月17日 週六 03:51
寫道:
>
>
> On 12/13/22 23:57, juzhe.zhong@rivai.ai wrote:
> > From: Ju-Zhe Zhong <juzhe.zhong@rivai.ai>
> >
> > This patch is preparing patch for the following patch (VSETVL PASS)
> > support since the current vlmul printing rule is not appropriate
> > information for VSETVL PASS. I split this fix in a single patch.
> >
> > gcc/ChangeLog:
> >
> > * config/riscv/riscv-v.cc (emit_vlmax_vsetvl): Pass through
> VLMUL enum instead of machine mode.
> > * config/riscv/riscv-vector-builtins-bases.cc: Ditto.
> > * config/riscv/riscv.cc (riscv_print_operand): Print LMUL by
> enum vlmul instead of machine mode.
> OK. Though I suspect your ChangeLog will need to be wrapped to get past
> the commit hooks.
>
> jeff
>
prev parent reply other threads:[~2022-12-19 15:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-14 6:57 juzhe.zhong
2022-12-16 19:50 ` Jeff Law
2022-12-19 15:07 ` Kito Cheng [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=CA+yXCZA_Uyrj6rAfRmZuH+yXJoJTRcrMwgdEhtQnedUc02MDSQ@mail.gmail.com \
--to=kito.cheng@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--cc=juzhe.zhong@rivai.ai \
--cc=palmer@dabbelt.com \
/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).