From: Jeff Law <jeffreyalaw@gmail.com>
To: Mariam Arutunian <mariamarutunian@gmail.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [RFC/RFA][PATCH v2 12/12] Add tests for CRC detection and generation.
Date: Sun, 25 Aug 2024 11:28:51 -0600 [thread overview]
Message-ID: <10b23a77-9f3c-48a3-b3dc-87addac10488@gmail.com> (raw)
In-Reply-To: <CAE65F3NcSA9Q_xG2OXiR9u8HmFWAFRhsKEY46gB8dkt-BbGZCw@mail.gmail.com>
On 7/26/24 12:07 PM, Mariam Arutunian wrote:
> gcc/testsuite/gcc.dg/torture/
>
> * crc-(1-29).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-coremark32-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-data24.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.
> * crc-linux-(1-5).c: Likewise.
> * crc-not-crc-(1-26).c: Likewise.
> * crc-side-instr-(1-17).c: Likewise.
>
> Signed-off-by: Mariam Arutunian <mariamarutunian@gmail.com
> <mailto:mariamarutunian@gmail.com>>
So I can't recall the state on all this stuff. So I'll go ahead and ACK
this (perhaps for the Nth time ;-) Obviously it can't commit until the
optimization bits are all in place.
Jeff
prev parent reply other threads:[~2024-08-25 17:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-26 18:07 Mariam Arutunian
2024-08-25 17:28 ` Jeff Law [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=10b23a77-9f3c-48a3-b3dc-87addac10488@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--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).