public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Joern Rennecke <joern.rennecke@embecosm.com>
To: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH v4 02/34] RISC-V: Add vlex_2.c
Date: Thu, 5 Jan 2023 16:26:53 +0000	[thread overview]
Message-ID: <CAMqJFCrB8Br02DeopKmCitZCyXBk--Bh7dm1qWeTEAF_vyNPUA@mail.gmail.com> (raw)

On Wed, Jun 1, 2022 at 02:28:45 GMT 2022, zhongjuzhe
<juzhe.zhong@rivai.ai> wrote:
> gcc/testsuite/ChangeLog:
>
>        * gcc.target/riscv/rvv/intrinsic/vlex_2.c: New test.

These intrinsic test cases look like they have been machine generated.  And if
they aren't, they probably should (have) be(en).  I've been working on
stabilizing
a tree with the rvv patches merged, and found a number of tests had diverged
in intrinsic function naming, arguments taken, and/or return type.
Fixing this all
with global replaces in dozens of files is quite messy.  It would be
preferable if
such issues could be fixed by adjusting a generator file, and just re-generating
the generated files.  That's one of the reasons why the GPL makes a point of
asking to include source code.  Even if that is not strictly required
for the testsuite
for license reasons, it makes good sense to do that for maintenance reasons.
The generator file should then also add a note where in the source
tree to find the
generator file, and, where appropriate, notes which part(s) of the
generator file
is/are responsible for generating the test case.

             reply	other threads:[~2023-01-05 16:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-05 16:26 Joern Rennecke [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-06-01  2:28 [PATCH 00/34] RISC-V: Add RVV (RISC-V 'V' Extension) support juzhe.zhong
2022-06-01  2:28 ` [PATCH v4 02/34] RISC-V: Add vlex_2.c juzhe.zhong

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=CAMqJFCrB8Br02DeopKmCitZCyXBk--Bh7dm1qWeTEAF_vyNPUA@mail.gmail.com \
    --to=joern.rennecke@embecosm.com \
    --cc=gcc-patches@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).