From: Kito Cheng <kito.cheng@gmail.com>
To: juzhe.zhong@rivai.ai
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] RISC-V: Add new line at end of file.
Date: Wed, 12 Oct 2022 21:00:15 +0800 [thread overview]
Message-ID: <CA+yXCZCDEVq1TQvLTdL_KiE5xcdavBkaGRbSqDynG7L22AFNeA@mail.gmail.com> (raw)
In-Reply-To: <20221012014236.301092-1-juzhe.zhong@rivai.ai>
Most changes has included in this commit:
https://github.com/gcc-mirror/gcc/commit/684d238b8cd7e8222d9e66457815f2a63178730b
On Wed, Oct 12, 2022 at 9:43 AM <juzhe.zhong@rivai.ai> wrote:
>
> From: Ju-Zhe Zhong <juzhe.zhong@rivai.ai>
>
> gcc/ChangeLog:
>
> * config/riscv/riscv-c.cc: Add new line.
> * config/riscv/riscv_vector.h (vwrite_csr): Add new line.
>
> ---
> gcc/config/riscv/riscv-c.cc | 2 +-
> gcc/config/riscv/riscv_vector.h | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/gcc/config/riscv/riscv-c.cc b/gcc/config/riscv/riscv-c.cc
> index 6fe4a8aeacf..57eeaebc582 100644
> --- a/gcc/config/riscv/riscv-c.cc
> +++ b/gcc/config/riscv/riscv-c.cc
> @@ -195,4 +195,4 @@ void
> riscv_register_pragmas (void)
> {
> c_register_pragma ("riscv", "intrinsic", riscv_pragma_intrinsic);
> -}
> \ No newline at end of file
> +}
> diff --git a/gcc/config/riscv/riscv_vector.h b/gcc/config/riscv/riscv_vector.h
> index 85cc656bc41..1efe3f888b5 100644
> --- a/gcc/config/riscv/riscv_vector.h
> +++ b/gcc/config/riscv/riscv_vector.h
> @@ -97,4 +97,4 @@ vwrite_csr(enum RVV_CSR csr, unsigned long value)
> }
> #endif // __cplusplus
> #endif // __riscv_vector
> -#endif // __RISCV_VECTOR_H
> \ No newline at end of file
> +#endif // __RISCV_VECTOR_H
> --
> 2.36.1
>
prev parent reply other threads:[~2022-10-12 13:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-12 1:42 juzhe.zhong
2022-10-12 13:00 ` 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+yXCZCDEVq1TQvLTdL_KiE5xcdavBkaGRbSqDynG7L22AFNeA@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).