public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Jeff Law <law@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc(refs/vendors/riscv/heads/gcc-13-with-riscv-opts)] RISC-V: Remove duplicate `#include "riscv-vector-switch.def"` Date: Mon, 19 Jun 2023 11:41:21 +0000 (GMT) [thread overview] Message-ID: <20230619114121.0C39C385842C@sourceware.org> (raw) https://gcc.gnu.org/g:17f9b68a95fb084daa02590ddc0890fd2e1cd948 commit 17f9b68a95fb084daa02590ddc0890fd2e1cd948 Author: Lehua Ding <lehua.ding@rivai.ai> Date: Tue Jun 13 18:59:09 2023 +0800 RISC-V: Remove duplicate `#include "riscv-vector-switch.def"` Hi, This patch remove the duplicate `#include "riscv-vector-switch.def"` statement and add #undef for ENTRY and TUPLE_ENTRY macros later. Best, Lehua gcc/ChangeLog: * config/riscv/riscv-v.cc (struct mode_vtype_group): Remove duplicate #include. (ENTRY): Undef. (TUPLE_ENTRY): Undef. Diff: --- gcc/config/riscv/riscv-v.cc | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/gcc/config/riscv/riscv-v.cc b/gcc/config/riscv/riscv-v.cc index d797326d736..e07d5c2901a 100644 --- a/gcc/config/riscv/riscv-v.cc +++ b/gcc/config/riscv/riscv-v.cc @@ -1254,7 +1254,6 @@ struct mode_vtype_group ratio_for_min_vlen64[MODE##mode] = RATIO_FOR_MIN_VLEN64; \ vlmul_for_for_vlen128[MODE##mode] = VLMUL_FOR_MIN_VLEN128; \ ratio_for_for_vlen128[MODE##mode] = RATIO_FOR_MIN_VLEN128; -#include "riscv-vector-switch.def" #define TUPLE_ENTRY(MODE, REQUIREMENT, SUBPART_MODE, NF, VLMUL_FOR_MIN_VLEN32, \ RATIO_FOR_MIN_VLEN32, VLMUL_FOR_MIN_VLEN64, \ RATIO_FOR_MIN_VLEN64, VLMUL_FOR_MIN_VLEN128, \ @@ -1268,6 +1267,8 @@ struct mode_vtype_group vlmul_for_for_vlen128[MODE##mode] = VLMUL_FOR_MIN_VLEN128; \ ratio_for_for_vlen128[MODE##mode] = RATIO_FOR_MIN_VLEN128; #include "riscv-vector-switch.def" +#undef ENTRY +#undef TUPLE_ENTRY } };
next reply other threads:[~2023-06-19 11:41 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-19 11:41 Jeff Law [this message] 2023-07-14 2:46 Jeff Law
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=20230619114121.0C39C385842C@sourceware.org \ --to=law@gcc.gnu.org \ --cc=gcc-cvs@gcc.gnu.org \ /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: linkBe 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).