From: Jonathan Wakely <jwakely@redhat.com>
To: libstdc++@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: [committed] libstdc++: Document linker option for C++23 <stacktrace> [PR105678]
Date: Mon, 22 Aug 2022 22:53:52 +0100 [thread overview]
Message-ID: <20220822215352.93012-1-jwakely@redhat.com> (raw)
Tested powerpc64le-linux, pushed to trunk. Needs backporting.
-- >8 --
libstdc++-v3/ChangeLog:
PR libstdc++/105678
* doc/xml/manual/using.xml: Document -lstdc++_libbacktrace
requirement for using std::stacktrace. Also adjust -frtti and
-fexceptions to document non-default (i.e. negative) forms.
* doc/html/*: Regenerate.
---
diff --git a/libstdc++-v3/doc/xml/manual/using.xml b/libstdc++-v3/doc/xml/manual/using.xml
index 36b86702d22..0b9a0c98518 100644
--- a/libstdc++-v3/doc/xml/manual/using.xml
+++ b/libstdc++-v3/doc/xml/manual/using.xml
@@ -69,12 +69,16 @@
</row>
<row>
- <entry><literal>-fexceptions</literal></entry>
+ <entry>
+ <literal>-fno-exceptions</literal>
+ </entry>
<entry>See <link linkend="intro.using.exception.no">exception-free dialect</link></entry>
</row>
<row>
- <entry><literal>-frtti</literal></entry>
+ <entry>
+ <literal>-fno-rtti</literal>
+ </entry>
<entry>As above, but RTTI-free dialect.</entry>
</row>
@@ -104,6 +108,17 @@
</entry>
</row>
+ <row>
+ <entry><literal>-lstdc++_libbacktrace</literal></entry>
+ <entry>Until C++23 support is non-experimental, linking to
+ <filename class="libraryfile">libstdc++_libbacktrace.a</filename>
+ is required for use of the C++23 type
+ <classname>std::stacktrace</classname>
+ and related types in
+ <filename class="headerfile"><stacktrace></filename>.
+ </entry>
+ </row>
+
<row>
<entry><literal>-fopenmp</literal></entry>
<entry>For <link linkend="manual.ext.parallel_mode">parallel</link> mode.</entry>
--
2.37.2
reply other threads:[~2022-08-22 21:53 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=20220822215352.93012-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).