public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Kito Cheng <kito@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r13-3254] RISC-V: Remove TUPLE size macro define. [NFC]
Date: Wed, 12 Oct 2022 12:52:48 +0000 (GMT)	[thread overview]
Message-ID: <20221012125248.0B3D73851170@sourceware.org> (raw)

https://gcc.gnu.org/g:fbf423309e103b54f7c9d39b2f7870b9bedfe9d2

commit r13-3254-gfbf423309e103b54f7c9d39b2f7870b9bedfe9d2
Author: Ju-Zhe Zhong <juzhe.zhong@rivai.ai>
Date:   Tue Oct 11 14:23:33 2022 +0800

    RISC-V: Remove TUPLE size macro define. [NFC]
    
    gcc/ChangeLog:
    
            * config/riscv/riscv-vector-builtins.h: Remove unused macro.

Diff:
---
 gcc/config/riscv/riscv-vector-builtins.h | 3 ---
 1 file changed, 3 deletions(-)

diff --git a/gcc/config/riscv/riscv-vector-builtins.h b/gcc/config/riscv/riscv-vector-builtins.h
index 7f4e89cd255..ea67da9905c 100644
--- a/gcc/config/riscv/riscv-vector-builtins.h
+++ b/gcc/config/riscv/riscv-vector-builtins.h
@@ -23,9 +23,6 @@
 
 namespace riscv_vector {
 
-/* This is for segment instructions.  */
-const unsigned int MAX_TUPLE_SIZE = 8;
-
 /* Enumerates the RVV types, together called
    "vector types" for brevity.  */
 enum vector_type_index

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

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20221012125248.0B3D73851170@sourceware.org \
    --to=kito@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: 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).