From: Jonathan Wakely <jwakely@redhat.com>
To: libstdc++@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: [committed] libstdc++: Fix spelling of <envar> elements in manual
Date: Fri, 16 Feb 2024 10:48:23 +0000 [thread overview]
Message-ID: <20240216104836.147940-1-jwakely@redhat.com> (raw)
Pushed to trunk.
-- >8 --
libstdc++-v3/ChangeLog:
* doc/xml/manual/test.xml: Fix spelling of <envar> elements.
* doc/html/manual/test.html: Regenerate.
---
libstdc++-v3/doc/html/manual/test.html | 4 ++--
libstdc++-v3/doc/xml/manual/test.xml | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/libstdc++-v3/doc/html/manual/test.html b/libstdc++-v3/doc/html/manual/test.html
index 4b7f60c9bad..3657997fad4 100644
--- a/libstdc++-v3/doc/html/manual/test.html
+++ b/libstdc++-v3/doc/html/manual/test.html
@@ -356,7 +356,7 @@ cat 27_io/objects/char/3_xin.in | a.out</pre></dd><dt><span class="term"><code c
<code class="envar">DEJAGNU</code> environment variable will cause every test to
be run three times, using a different <code class="option">-std</code> each time.
Alternatively, a list of standard versions to test with can be specified
- as a comma-separated list in the <span style="color: red"><envvar>GLIBCXX_TESTSUITE_STDS</envvar></span>
+ as a comma-separated list in the <code class="envar">GLIBCXX_TESTSUITE_STDS</code>
environment variable.
</p><p>
To run the libstdc++ test suite under the
@@ -478,7 +478,7 @@ cat 27_io/objects/char/3_xin.in | a.out</pre></dd><dt><span class="term"><code c
the test will be skipped by default unless <code class="option">-std=gnu++11</code>
or <code class="option">-std=c++11</code> is explicitly specified, either via a
target board, the <code class="varname">v3_std_list</code> dejagnu variable,
- or the <span style="color: red"><envvar>GLIBCXX_TESTSUITE_STDS</envvar></span> environment variable.
+ or the <code class="envar">GLIBCXX_TESTSUITE_STDS</code> environment variable.
For tests that require a specific standard it is useful to also add a
<code class="literal">dg-options</code> directive:
</p><pre class="programlisting"> // { dg-options "-std=gnu++11" }</pre><p>
diff --git a/libstdc++-v3/doc/xml/manual/test.xml b/libstdc++-v3/doc/xml/manual/test.xml
index f2c709bc6bf..40926946fe7 100644
--- a/libstdc++-v3/doc/xml/manual/test.xml
+++ b/libstdc++-v3/doc/xml/manual/test.xml
@@ -604,7 +604,7 @@ cat 27_io/objects/char/3_xin.in | a.out</programlisting>
<envar>DEJAGNU</envar> environment variable will cause every test to
be run three times, using a different <option>-std</option> each time.
Alternatively, a list of standard versions to test with can be specified
- as a comma-separated list in the <envvar>GLIBCXX_TESTSUITE_STDS</envvar>
+ as a comma-separated list in the <envar>GLIBCXX_TESTSUITE_STDS</envar>
environment variable.
</para>
@@ -779,7 +779,7 @@ cat 27_io/objects/char/3_xin.in | a.out</programlisting>
the test will be skipped by default unless <option>-std=gnu++11</option>
or <option>-std=c++11</option> is explicitly specified, either via a
target board, the <varname>v3_std_list</varname> dejagnu variable,
- or the <envvar>GLIBCXX_TESTSUITE_STDS</envvar> environment variable.
+ or the <envar>GLIBCXX_TESTSUITE_STDS</envar> environment variable.
For tests that require a specific standard it is useful to also add a
<literal>dg-options</literal> directive:
<programlisting> // { dg-options "-std=gnu++11" }</programlisting>
--
2.43.0
reply other threads:[~2024-02-16 10:48 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=20240216104836.147940-1-jwakely@redhat.com \
--to=jwakely@redhat.com \
--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).