From: Keith Packard <keithp@keithp.com>
To: libstdc++@gcc.gnu.org
Cc: gcc-patches@gcc.gnu.org, Keith Packard <keithp@keithp.com>
Subject: [PATCH 0/2] Support libc with stdio-only I/O in libstdc++
Date: Wed, 9 Dec 2020 18:46:55 -0800 [thread overview]
Message-ID: <20201210024657.3395687-1-keithp@keithp.com> (raw)
In-Reply-To: <20201209101700.GS2309743@redhat.com>
The current libstdc++ basic_file_stdio.cc code assumes a POSIX API
underneath the stdio implementation provided by the host libc. This
means that the host must provide a fairly broad POSIX file API,
including read, write, open, close, lseek and ioctl.
This patch changes basic_file_stdio.cc to only use basic ANSI-C stdio
functions, allowing it to be used with libc implementations like
picolibc which may not have a POSIX operating system underneath.
This is version 2 of the patch. This version uses the existing
--enable-stdio option, extending that to add 'stdio_pure' for this
mode using a patch created by Jonathan Wakely <jwakely@redhat.com>
next prev parent reply other threads:[~2020-12-10 2:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-07 18:39 Keith Packard
2020-12-07 18:39 ` [PATCH 1/2] libstdc++: Add --enable-pure-stdio-libstdcxx option Keith Packard
2020-12-07 18:55 ` Jonathan Wakely
2020-12-07 20:36 ` Keith Packard
2020-12-09 10:17 ` Jonathan Wakely
2020-12-09 16:32 ` Keith Packard
2020-12-09 16:52 ` Jonathan Wakely
2020-12-10 2:46 ` Keith Packard [this message]
2020-12-10 2:46 ` [PATCH 1/2] libstdc++: Add --enable-stdio=stdio_pure option [v2] Keith Packard
2020-12-10 20:23 ` Jonathan Wakely
2020-12-10 20:56 ` Keith Packard
2020-12-15 18:43 ` Jonathan Wakely
2020-12-10 2:46 ` [PATCH 2/2] Regenerate libstdc++-v3 autoconf files Keith Packard
2020-12-07 18:39 ` Keith Packard
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=20201210024657.3395687-1-keithp@keithp.com \
--to=keithp@keithp.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).