public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Kito Cheng <kito.cheng@gmail.com>
To: juzhe.zhong@rivai.ai
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] RISC-V: Clang-format add_vector_attribute function.
Date: Wed, 12 Oct 2022 21:03:10 +0800	[thread overview]
Message-ID: <CA+yXCZC+=oBh6v=BsOky1T+bkxKi1TRebT30FUMtUL-GHsRNPA@mail.gmail.com> (raw)
In-Reply-To: <20221011062159.69697-1-juzhe.zhong@rivai.ai>

Committed, thanks!

On Tue, Oct 11, 2022 at 2:22 PM <juzhe.zhong@rivai.ai> wrote:
>
> From: Ju-Zhe Zhong <juzhe.zhong@rivai.ai>
>
> gcc/ChangeLog:
>
>         * config/riscv/riscv-vector-builtins.cc (add_vector_type_attribute): Clang-format function.
>
> ---
>  gcc/config/riscv/riscv-vector-builtins.cc | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/gcc/config/riscv/riscv-vector-builtins.cc b/gcc/config/riscv/riscv-vector-builtins.cc
> index daf180801cc..4814b6ef6e7 100644
> --- a/gcc/config/riscv/riscv-vector-builtins.cc
> +++ b/gcc/config/riscv/riscv-vector-builtins.cc
> @@ -88,8 +88,8 @@ add_vector_type_attribute (tree type, const char *mangled_name)
>  {
>    tree mangled_name_tree = get_identifier (mangled_name);
>    tree value = tree_cons (NULL_TREE, mangled_name_tree, NULL_TREE);
> -  TYPE_ATTRIBUTES (type) = tree_cons (get_identifier ("RVV type"), value,
> -                                     TYPE_ATTRIBUTES (type));
> +  TYPE_ATTRIBUTES (type)
> +    = tree_cons (get_identifier ("RVV type"), value, TYPE_ATTRIBUTES (type));
>  }
>
>  /* Force TYPE to be a sizeless type.  */
> --
> 2.36.1
>

      reply	other threads:[~2022-10-12 13:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-11  6:21 juzhe.zhong
2022-10-12 13:03 ` 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+yXCZC+=oBh6v=BsOky1T+bkxKi1TRebT30FUMtUL-GHsRNPA@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).