From: Richard Biener <richard.guenther@gmail.com>
To: Jeff Law <jeffreyalaw@gmail.com>
Cc: Mariam Arutunian <mariamarutunian@gmail.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [RFC/RFA] [PATCH 12/12] Add tests for CRC detection and generation.
Date: Mon, 27 May 2024 08:39:51 +0200 [thread overview]
Message-ID: <CAFiYyc1ybL6_xDpAyVj4f=ZvQXBvbtjRiMe8uxuK3KrLQxNnyA@mail.gmail.com> (raw)
In-Reply-To: <58a12695-981a-4c0e-b464-ce67ebac625b@gmail.com>
On Sat, May 25, 2024 at 8:34 PM Jeff Law <jeffreyalaw@gmail.com> wrote:
>
>
>
> On 5/24/24 2:42 AM, Mariam Arutunian wrote:
> > gcc/testsuite/gcc.c-torture/compile/
> >
> > * crc-11.c: New test.
> > * crc-15.c: Likewise.
> > * crc-16.c: Likewise.
> > * crc-19.c: Likewise.
> > * crc-2.c: Likewise.
> > * crc-20.c: Likewise.
> > * crc-24.c: Likewise.
> > * crc-29.c: Likewise.
> > * crc-27.c: Likewise.
> > * crc-3.c: Likewise.
> > * crc-crc32-data24.c: Likewise.
> > * crc-from-fedora-packages (1-24).c: Likewise.
> > * crc-linux-(1-5).c: Likewise.
> > * crc-not-crc-(1-26).c: Likewise.
> > * crc-side-instr-(1-17).c: Likewise.
> >
> > gcc/testsuite/gcc.c-torture/execute/
> >
> > * crc-(1, 4-10, 12-14, 17-18, 21-28).c: New tests.
> > * crc-CCIT-data16-xorOutside_InsideFor.c: Likewise.
> > * crc-CCIT-data16.c: Likewise.
> > * crc-CCIT-data8.c: Likewise.
> > * crc-coremark16-data16.c: Likewise.
> > * crc-coremark16-data16.c: Likewise.
> > * crc-coremark32-data32.c: Likewise.
> > * crc-coremark32-data8.c: Likewise.
> > * crc-coremark64-data64.c: Likewise.
> > * crc-coremark8-data8.c: Likewise.
> > * crc-crc32-data16.c: Likewise.
> > * crc-crc32-data8.c: Likewise.
> > * crc-crc32.c: Likewise.
> > * crc-crc64-data32.c: Likewise.
> > * crc-crc64-data64.c: Likewise.
> > * crc-crc8-data8-loop-xorInFor.c: Likewise.
> > * crc-crc8-data8-loop-xorOutsideFor.c: Likewise.
> > * crc-crc8-data8-xorOustideFor.c: Likewise.
> > * crc-crc8.c: Likewise.
> >
> > Signed-off-by: Mariam Arutunian <mariamarutunian@gmail.com
> > <mailto:mariamarutunian@gmail.com>>
> OK once all prerequisites are approved.
At some point gcc.c-torture/ was considered "legacy", is that no longer
true? I'd prefer if you add these tests to gcc.dg/torture/ instead.
Richard.
> jeff
>
next prev parent reply other threads:[~2024-05-27 6:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-24 8:42 Mariam Arutunian
2024-05-25 18:34 ` Jeff Law
2024-05-26 5:02 ` Mariam Arutunian
2024-05-27 6:39 ` Richard Biener [this message]
2024-05-27 15:20 ` 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='CAFiYyc1ybL6_xDpAyVj4f=ZvQXBvbtjRiMe8uxuK3KrLQxNnyA@mail.gmail.com' \
--to=richard.guenther@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--cc=mariamarutunian@gmail.com \
/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).