public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely@redhat.com>
To: Keith Packard <keithp@keithp.com>
Cc: libstdc++@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH 1/2] libstdc++: Add --enable-stdio=stdio_pure option [v2]
Date: Thu, 10 Dec 2020 20:23:06 +0000	[thread overview]
Message-ID: <20201210202306.GD2309743@redhat.com> (raw)
In-Reply-To: <20201210024657.3395687-2-keithp@keithp.com>

On 09/12/20 18:46 -0800, Keith Packard wrote:
>This option directs the library to only use simple stdio APIs instead
>of using fileno to get the file descriptor for use with POSIX APIs.

This looks fine to me, even at this stage of GCC 11 (it doesn't affect
the default configurations, just adds a new one that nobody is going
to use unless they ask for it explicitly).

I'll do a bit more testing and push it next week.

Thanks for the patch!


  reply	other threads:[~2020-12-10 20:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20201207183927.3275768-1-keithp@keithp.com>
     [not found] ` <20201207183927.3275768-2-keithp@keithp.com>
2020-12-07 18:55   ` [PATCH 1/2] libstdc++: Add --enable-pure-stdio-libstdcxx option 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         ` [PATCH 0/2] Support libc with stdio-only I/O in libstdc++ Keith Packard
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 [this message]
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

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=20201210202306.GD2309743@redhat.com \
    --to=jwakely@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=keithp@keithp.com \
    --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).