From: Matthias Kretz <m.kretz@gsi.de>
To: <gcc-patches@gcc.gnu.org>, <libstdc++@gcc.gnu.org>
Subject: [PATCH 0/3] Improve and document stdx::simd testsuite
Date: Tue, 8 Jun 2021 10:57:20 +0200 [thread overview]
Message-ID: <2392568.8UF1cRMu57@excalibur> (raw)
As discussed a long time ago on IRC, this improves (i.e. decreases by default)
the verbosity of make check-simd, gives more verbosity options, and finally
documents how the simd testsuite is used and how it works. In addition, after
PR98834 was resolved, remove the -fno-tree-vrp workaround.
Tested on x86_64-linux (and more).
Matthias Kretz (3):
libstdc++: Remove -fno-tree-vrp after PR98834 was resolved
libstdc++: Improve output verbosity options and default
libstdc++: Document simd testsuite
libstdc++-v3/testsuite/Makefile.am | 3 +-
libstdc++-v3/testsuite/Makefile.in | 3 +-
.../testsuite/experimental/simd/README.md | 257 ++++++++++++++++++
.../testsuite/experimental/simd/driver.sh | 137 +++++++---
.../experimental/simd/generate_makefile.sh | 33 ++-
5 files changed, 380 insertions(+), 53 deletions(-)
create mode 100644 libstdc++-v3/testsuite/experimental/simd/README.md
--
──────────────────────────────────────────────────────────────────────────
Dr. Matthias Kretz https://mattkretz.github.io
GSI Helmholtz Centre for Heavy Ion Research https://gsi.de
std::experimental::simd https://github.com/VcDevel/std-simd
──────────────────────────────────────────────────────────────────────────
next reply other threads:[~2021-06-08 8:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-08 8:57 Matthias Kretz [this message]
2021-06-08 8:58 ` [PATCH 1/3] libstdc++: Remove -fno-tree-vrp after PR98834 was resolved Matthias Kretz
2021-06-08 8:59 ` [PATCH 2/3] libstdc++: Improve output verbosity options and default Matthias Kretz
2021-06-08 8:59 ` [PATCH 3/3] libstdc++: Document simd testsuite Matthias Kretz
2021-06-23 15:46 ` [PATCH 0/3] Improve and document stdx::simd testsuite Jonathan Wakely
2021-06-24 13:12 ` Jonathan Wakely
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=2392568.8UF1cRMu57@excalibur \
--to=m.kretz@gsi.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=libstdc++@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).