From: Matthew Joyce <matthew.joyce@embedded-brains.de>
To: newlib@sourceware.org
Subject: [PATCH 00/11] Decouple global file object list from _GLOBAL_REENT
Date: Tue, 10 May 2022 10:09:16 +0200 [thread overview]
Message-ID: <20220510080927.28839-1-matthew.joyce@embedded-brains.de> (raw)
From: Matt Joyce <matthew.joyce@embedded-brains.de>
The _GLOBAL_REENT structure maintains global information across threads,
including a global list of open file objects. This patch set aims to
decouple the global file object list from _GLOBAL_REENT, reducing dependency
on the structure.
This is accomplished by:
1) Simplifying stdio and __sglue initializations
2) Adding a dedicated stdio atexit handler
3) Adding a global __sglue object and removing __sglue from struct _reent for
certain configurations
This effort will facilitate the future addition of a thread-local storage
configuration option as an alternative to using struct _reent.
Matt Joyce (9):
Remove duplicate stdio initializations
Remove duplicate sglue initializations
Add two __sglue initialization macros
Remove __sinit_locks / __sinit_recursive_mutex
Move __sglue initializations to __sfp()
Add CLEANUP_FILE define
Add stdio atexit handler
Add global __sglue object for all configurations
Remove __sglue member for one configuration
Sebastian Huber (2):
Declare global __sf[] only once
stdio: Replace _fwalk_reent() with _fwalk_sglue()
newlib/libc/include/sys/reent.h | 21 ++++--
newlib/libc/reent/reent.c | 6 +-
newlib/libc/stdio/fcloseall.c | 9 ++-
newlib/libc/stdio/fflush.c | 2 +-
newlib/libc/stdio/findfp.c | 112 +++++++++++++++++---------------
newlib/libc/stdio/fwalk.c | 15 +++--
newlib/libc/stdio/local.h | 6 +-
newlib/libc/stdio/refill.c | 4 +-
newlib/libc/stdlib/exit.c | 6 +-
winsup/cygwin/signal.cc | 5 +-
winsup/cygwin/syscalls.cc | 5 +-
11 files changed, 110 insertions(+), 81 deletions(-)
--
2.31.1
next reply other threads:[~2022-05-10 8:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-10 8:09 Matthew Joyce [this message]
2022-05-10 8:09 ` [PATCH 01/11] Remove duplicate stdio initializations Matthew Joyce
2022-05-10 8:09 ` [PATCH 02/11] Remove duplicate sglue initializations Matthew Joyce
2022-05-10 8:09 ` [PATCH 03/11] Declare global __sf[] only once Matthew Joyce
2022-05-10 8:09 ` [PATCH 04/11] Add two __sglue initialization macros Matthew Joyce
2022-05-10 8:09 ` [PATCH 05/11] Remove __sinit_locks / __sinit_recursive_mutex Matthew Joyce
2022-05-10 8:09 ` [PATCH 06/11] Move __sglue initializations to __sfp() Matthew Joyce
2022-05-10 8:09 ` [PATCH 07/11] Add CLEANUP_FILE define Matthew Joyce
2022-05-10 8:09 ` [PATCH 08/11] Add stdio atexit handler Matthew Joyce
2022-05-11 15:23 ` Corinna Vinschen
2022-05-11 16:54 ` Corinna Vinschen
2022-05-11 17:51 ` Sebastian Huber
2022-05-11 17:51 ` Sebastian Huber
2022-05-10 8:09 ` [PATCH 09/11] stdio: Replace _fwalk_reent() with _fwalk_sglue() Matthew Joyce
2022-05-11 15:56 ` Corinna Vinschen
2022-05-11 17:55 ` Sebastian Huber
2022-05-12 7:59 ` Corinna Vinschen
2022-05-10 8:09 ` [PATCH 10/11] Add global __sglue object for all configurations Matthew Joyce
2022-05-10 8:09 ` [PATCH 11/11] Remove __sglue member for one configuration Matthew Joyce
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=20220510080927.28839-1-matthew.joyce@embedded-brains.de \
--to=matthew.joyce@embedded-brains.de \
--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).