From: Jonathan Wakely <jwakely@redhat.com>
To: libstdc++@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: [committed] libstdc++: Document --enable-cstdio=stdio_pure [PR110574]
Date: Thu, 6 Jul 2023 16:28:02 +0100 [thread overview]
Message-ID: <20230706152826.1254690-1-jwakely@redhat.com> (raw)
Pushed to trunk. Backports to 11, 12 and 13 will follow.
-- >8 --
libstdc++-v3/ChangeLog:
PR libstdc++/110574
* doc/xml/manual/configure.xml: Describe stdio_pure argument to
--enable-cstdio.
* doc/html/manual/configure.html: Regenerate.
---
libstdc++-v3/doc/html/manual/configure.html | 11 ++++++++---
libstdc++-v3/doc/xml/manual/configure.xml | 11 ++++++++---
2 files changed, 16 insertions(+), 6 deletions(-)
diff --git a/libstdc++-v3/doc/xml/manual/configure.xml b/libstdc++-v3/doc/xml/manual/configure.xml
index 7ff07aea886..1b8c37ce2a9 100644
--- a/libstdc++-v3/doc/xml/manual/configure.xml
+++ b/libstdc++-v3/doc/xml/manual/configure.xml
@@ -74,9 +74,14 @@
</listitem></varlistentry>
<varlistentry><term><code>--enable-cstdio=OPTION</code></term>
- <listitem><para>Select a target-specific I/O package. At the moment, the only
- choice is to use 'stdio', a generic "C" abstraction.
- The default is 'stdio'. This option can change the library ABI.
+ <listitem><para>Select a target-specific I/O package. The choices are 'stdio'
+ which is a generic abstraction using POSIX file I/O APIs
+ (<function>read</function>, <function>write</function>,
+ <function>lseek</function>, etc.), and 'stdio_pure' which is similar
+ but only uses standard C file I/O APIs (<function>fread</function>,
+ <function>fwrite</function>, <function>fseek</function>, etc.).
+ The 'stdio_posix' choice is a synonym for 'stdio'.
+ The default is 'stdio'. This option can change the library ABI.
</para>
</listitem></varlistentry>
--
2.41.0
reply other threads:[~2023-07-06 15:35 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=20230706152826.1254690-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).