public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Jonathan Wakely <redi@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org Subject: [gcc r12-1779] libstdc++: Fix typos and markdown errors in new simd/README.md Date: Thu, 24 Jun 2021 13:09:57 +0000 (GMT) [thread overview] Message-ID: <20210624130957.EB8EB382C421@sourceware.org> (raw) https://gcc.gnu.org/g:07ba52849ffca26a3d461f94921b23a9cdbaea7f commit r12-1779-g07ba52849ffca26a3d461f94921b23a9cdbaea7f Author: Jonathan Wakely <jwakely@redhat.com> Date: Thu Jun 24 13:49:19 2021 +0100 libstdc++: Fix typos and markdown errors in new simd/README.md Signed-off-by: Jonathan Wakely <jwakely@redhat.com> libstdc++-v3/ChangeLog: * testsuite/experimental/simd/README.md: Fix typos. Diff: --- libstdc++-v3/testsuite/experimental/simd/README.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/libstdc++-v3/testsuite/experimental/simd/README.md b/libstdc++-v3/testsuite/experimental/simd/README.md index db0d71f8d43..b82453df403 100644 --- a/libstdc++-v3/testsuite/experimental/simd/README.md +++ b/libstdc++-v3/testsuite/experimental/simd/README.md @@ -11,7 +11,7 @@ the environment variables documented below. ### `target_list` Similar to dejagnu target lists: E.g. -`target_list="unix{-march=sandybridge,-march=native/-ffast-math,-march=native/-ffinite-math-only}" +`target_list="unix{-march=sandybridge,-march=native/-ffast-math,-march=native/-ffinite-math-only}"` would create three subdirs in `testsuite/simd/` to run the complete simd testsuite first with `-march=sandybridge`, then with `-march=native -ffast-math`, and finally with `-march=native -ffinite-math-only`. @@ -21,7 +21,7 @@ testsuite first with `-march=sandybridge`, then with `-march=native This variable can be set to a path to a file which is equivalent to a dejagnu board. The file needs to be a valid `sh` script since it is sourced from the -`scripts/check_simd` script. It's purpose is to set the `target_list` variable +`scripts/check_simd` script. Its purpose is to set the `target_list` variable depending on `$target_triplet` (or whatever else makes sense for you). Example: ```sh @@ -52,7 +52,7 @@ the `target_list` variable. In the example above `define_target power7 `power7` which always uses the flags `-mcpu=power7` and `-static` when compiling tests and prepends `$HOME/bin/run_on_gccfarm gcc112` to test executables. In `target_list` you can now use the name `power7`. E.g. -`target_list="power7 power7/-ffast-math"` or it's shorthand +`target_list="power7 power7/-ffast-math"` or its shorthand `target_list="power7{,-ffast-math}"`. @@ -109,7 +109,7 @@ A test starts with the copyright header, directly followed by directives influencing the set of tests to generate and whether the test driver should expect a failure. -Then the test must at least `#include "bits/verify.h", which provides `main` +Then the test must at least `#include "bits/verify.h"`, which provides `main` and declares a `template <typename V> void test()` function, which the test has to define. The template parameter is set to `simd<T, Abi>` type where `T` and `Abi` are determined by the type and ABI subset dimensions.
reply other threads:[~2021-06-24 13:09 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=20210624130957.EB8EB382C421@sourceware.org \ --to=redi@gcc.gnu.org \ --cc=gcc-cvs@gcc.gnu.org \ --cc=libstdc++-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: linkBe 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).