From: Kito Cheng <kito.cheng@gmail.com>
To: Robin Dapp <rdapp.gcc@gmail.com>
Cc: "Richard Biener" <richard.guenther@gmail.com>,
"Robin Dapp via Gcc-patches" <gcc-patches@gcc.gnu.org>,
钟居哲 <juzhe.zhong@rivai.ai>, "Jeff Law" <jeffreyalaw@gmail.com>,
"kito.cheng" <kito.cheng@sifive.com>, palmer <palmer@dabbelt.com>,
palmer <palmer@rivosinc.com>,
richard.sandiford@arm.com
Subject: Re: [PATCH V3] RISC-V: Fix bug of pre-calculated const vector mask for VNx1BI, VNx2BI and VNx4BI
Date: Thu, 29 Jun 2023 21:53:04 +0800 [thread overview]
Message-ID: <CA+yXCZASzv6CxAyEheUbjhP=Y6Gd7g2FDXgM3+KNu1VNdpqnHQ@mail.gmail.com> (raw)
In-Reply-To: <5c3171e3-fc51-05fa-a018-a1e750a3b4d0@gmail.com>
Hi Robin:
> diff --git a/gcc/lto/lto-lang.cc b/gcc/lto/lto-lang.cc
> index 52d7626e92e..14d419c2013 100644
> --- a/gcc/lto/lto-lang.cc
> +++ b/gcc/lto/lto-lang.cc
> @@ -1050,7 +1050,7 @@ lto_type_for_mode (machine_mode mode, int unsigned_p)
> else if (GET_MODE_CLASS (mode) == MODE_VECTOR_BOOL
> && valid_vector_subparts_p (GET_MODE_NUNITS (mode)))
> {
> - unsigned int elem_bits = vector_element_size (GET_MODE_BITSIZE (mode),
> + unsigned int elem_bits = vectwhereor_element_size (GET_MODE_PRECISION (mode),
This seems weird?
> GET_MODE_NUNITS (mode));
> tree bool_type = build_nonstandard_boolean_type (elem_bits);
> return build_vector_type_for_mode (bool_type, mode);
next prev parent reply other threads:[~2023-06-29 13:53 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-28 9:47 Juzhe-Zhong
2023-06-28 18:11 ` Jeff Law
2023-06-28 19:02 ` 钟居哲
2023-06-28 19:12 ` Robin Dapp
2023-06-28 20:42 ` Richard Sandiford
2023-06-28 21:46 ` 钟居哲
2023-06-29 7:53 ` Richard Sandiford
2023-06-29 8:08 ` juzhe.zhong
2023-06-29 8:14 ` Robin Dapp
2023-06-29 8:18 ` juzhe.zhong
2023-06-29 8:53 ` Robin Dapp
2023-06-29 9:01 ` juzhe.zhong
2023-06-29 8:54 ` Richard Sandiford
2023-06-29 9:09 ` Robin Dapp
2023-06-29 9:23 ` juzhe.zhong
2023-06-29 11:22 ` Richard Biener
2023-06-29 11:38 ` Robin Dapp
2023-06-29 13:53 ` Kito Cheng [this message]
2023-06-29 14:04 ` Richard Sandiford
2023-06-29 14:12 ` Robin Dapp
2023-07-04 19:07 ` Robin Dapp
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+yXCZASzv6CxAyEheUbjhP=Y6Gd7g2FDXgM3+KNu1VNdpqnHQ@mail.gmail.com' \
--to=kito.cheng@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--cc=juzhe.zhong@rivai.ai \
--cc=kito.cheng@sifive.com \
--cc=palmer@dabbelt.com \
--cc=palmer@rivosinc.com \
--cc=rdapp.gcc@gmail.com \
--cc=richard.guenther@gmail.com \
--cc=richard.sandiford@arm.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).