public inbox for newlib@sourceware.org
 help / color / mirror / Atom feed
From: Corinna Vinschen <vinschen@redhat.com>
To: newlib@sourceware.org
Subject: Re: [PATCH v2] Use global stdio streams for all configurations
Date: Fri, 10 Jun 2022 13:52:56 +0200	[thread overview]
Message-ID: <YqMwmKmVESD44bMo@calimero.vinschen.de> (raw)
In-Reply-To: <f4d742d1-695b-6a09-05bf-d6c5381a5938@embedded-brains.de>

On Jun 10 13:41, Sebastian Huber wrote:
> On 10.06.22 12:45, Corinna Vinschen wrote:
> > On Jun  8 11:43, Sebastian Huber wrote:
> > > The _REENT_GLOBAL_STDIO_STREAMS was introduced by commit
> > > 668a4c8722090fffd10869dbb15b879651c1370d in 2017.  Since then it was enabled by
> > > [...]
> > >   newlib/README                         |   6 --
> > >   newlib/configure.ac                   |  10 +--
> > >   newlib/libc/include/sys/config.h      |   7 --
> > >   newlib/libc/include/sys/reent.h       | 118 +++-----------------------
> > >   newlib/libc/reent/impure.c            |   6 --
> > >   newlib/libc/reent/reent.c             |  20 -----
> > >   newlib/libc/stdio/fcloseall.c         |   4 -
> > >   newlib/libc/stdio/findfp.c            |  53 +-----------
> > >   newlib/libc/stdio/local.h             |  17 ----
> > >   winsup/cygwin/include/cygwin/config.h |   1 -
> > >   10 files changed, 14 insertions(+), 228 deletions(-)
> > LGTM together with your "Fix __fp_lock_all() and __fp_unlock_all()" patch.
> 
> Thanks for having a look at it. I am on holidays next week. Should I still
> check it in today?

Sure, no worries.

Thx,
Corinna


  reply	other threads:[~2022-06-10 11:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-08  9:43 Sebastian Huber
2022-06-10 10:45 ` Corinna Vinschen
2022-06-10 11:41   ` Sebastian Huber
2022-06-10 11:52     ` Corinna Vinschen [this message]
2022-06-17 11:33   ` Volodymyr Medvid

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=YqMwmKmVESD44bMo@calimero.vinschen.de \
    --to=vinschen@redhat.com \
    --cc=newlib@sourceware.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).