From: Sebastian Huber <sebastian.huber@embedded-brains.de>
To: Newlib <newlib@sourceware.org>
Subject: Re: Optionally use thread-local objects for struct _reent members
Date: Thu, 19 May 2022 10:49:38 +0200 [thread overview]
Message-ID: <7bc2dc3d-3e9c-2b1d-7d8a-fd00d17ba237@embedded-brains.de> (raw)
In-Reply-To: <32452837-4a35-d458-c971-c5c1e4f92290@embedded-brains.de>
Hello,
I just would like to give a short status update.
With the recent patches using _REENT_GLOBAL is no longer required. The
global state of Newlib is managed by dedicated objects (for example the
FILE object list or the exit handlers). This enables us to use
thread-local objects for all members of struct _reent. We should have a
patch ready for review soon.
It would help if we could make the _REENT_GLOBAL_STDIO_STREAMS option
the default behaviour and remove the associated conditional code. It is
currently enabled by Cygwin and RTEMS. I will send a patch to discuss
this next week.
We didn't work on the support for constructors/destructors for
thread-local objects yet, see:
https://www.openwall.com/lists/libc-coord/2022/01/21/1
My approach would be to first add a prototype implementation to Newlib
using a dedicated linker set and then make a proposal for the ELF support.
--
embedded brains GmbH
Herr Sebastian HUBER
Dornierstr. 4
82178 Puchheim
Germany
email: sebastian.huber@embedded-brains.de
phone: +49-89-18 94 741 - 16
fax: +49-89-18 94 741 - 08
Registergericht: Amtsgericht München
Registernummer: HRB 157899
Vertretungsberechtigte Geschäftsführer: Peter Rasmussen, Thomas Dörfler
Unsere Datenschutzerklärung finden Sie hier:
https://embedded-brains.de/datenschutzerklaerung/
prev parent reply other threads:[~2022-05-19 8:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-10 9:28 Sebastian Huber
2022-01-10 12:56 ` Corinna Vinschen
2022-01-10 16:26 ` Sebastian Huber
2022-05-19 8:49 ` Sebastian Huber [this message]
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=7bc2dc3d-3e9c-2b1d-7d8a-fd00d17ba237@embedded-brains.de \
--to=sebastian.huber@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).