From: Kito Cheng <kito.cheng@gmail.com>
To: juzhe.zhong@rivai.ai
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] RISC-V: Reorganize mangle_builtin_type.[NFC]
Date: Mon, 17 Oct 2022 16:05:16 +0800 [thread overview]
Message-ID: <CA+yXCZBoruoNDcSEoSWrLw8SyskbOrMC=7aTzCsrKbgRws8muQ@mail.gmail.com> (raw)
In-Reply-To: <20221014230236.134044-1-juzhe.zhong@rivai.ai>
Committed :)
On Sat, Oct 15, 2022 at 7:03 AM <juzhe.zhong@rivai.ai> wrote:
>
> From: Ju-Zhe Zhong <juzhe.zhong@rivai.ai>
>
> Hi, this patch fixed my mistake in the previous commit patch.
> Since "mangle_builtin_type" is a global function will be called in riscv.cc.
> It's reasonable move it down and put them together stay with other global functions.
>
> gcc/ChangeLog:
>
> * config/riscv/riscv-vector-builtins.cc (mangle_builtin_type): Move down the function.
> ---
> gcc/config/riscv/riscv-vector-builtins.cc | 26 +++++++++++------------
> 1 file changed, 13 insertions(+), 13 deletions(-)
>
> diff --git a/gcc/config/riscv/riscv-vector-builtins.cc b/gcc/config/riscv/riscv-vector-builtins.cc
> index 99c482582d3..55d45651618 100644
> --- a/gcc/config/riscv/riscv-vector-builtins.cc
> +++ b/gcc/config/riscv/riscv-vector-builtins.cc
> @@ -155,19 +155,6 @@ lookup_vector_type_attribute (const_tree type)
> return lookup_attribute ("RVV type", TYPE_ATTRIBUTES (type));
> }
>
> -/* If TYPE is a built-in type defined by the RVV ABI, return the mangled name,
> - otherwise return NULL. */
> -const char *
> -mangle_builtin_type (const_tree type)
> -{
> - if (TYPE_NAME (type) && TREE_CODE (TYPE_NAME (type)) == TYPE_DECL)
> - type = TREE_TYPE (TYPE_NAME (type));
> - if (tree attr = lookup_vector_type_attribute (type))
> - if (tree id = TREE_VALUE (chain_index (0, TREE_VALUE (attr))))
> - return IDENTIFIER_POINTER (id);
> - return NULL;
> -}
> -
> /* Return a representation of "const T *". */
> static tree
> build_const_pointer (tree t)
> @@ -250,6 +237,19 @@ register_vector_type (vector_type_index type)
> builtin_types[type].vector_ptr = build_pointer_type (vectype);
> }
>
> +/* If TYPE is a built-in type defined by the RVV ABI, return the mangled name,
> + otherwise return NULL. */
> +const char *
> +mangle_builtin_type (const_tree type)
> +{
> + if (TYPE_NAME (type) && TREE_CODE (TYPE_NAME (type)) == TYPE_DECL)
> + type = TREE_TYPE (TYPE_NAME (type));
> + if (tree attr = lookup_vector_type_attribute (type))
> + if (tree id = TREE_VALUE (chain_index (0, TREE_VALUE (attr))))
> + return IDENTIFIER_POINTER (id);
> + return NULL;
> +}
> +
> /* Initialize all compiler built-ins related to RVV that should be
> defined at start-up. */
> void
> --
> 2.36.1
>
prev parent reply other threads:[~2022-10-17 8:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-14 23:02 juzhe.zhong
2022-10-17 8:05 ` 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+yXCZBoruoNDcSEoSWrLw8SyskbOrMC=7aTzCsrKbgRws8muQ@mail.gmail.com' \
--to=kito.cheng@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=juzhe.zhong@rivai.ai \
/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).