From: Sebastian Huber <sebastian.huber@embedded-brains.de>
To: newlib@sourceware.org
Subject: Re: Optionally use thread-local objects for struct _reent members
Date: Mon, 10 Jan 2022 17:26:53 +0100 [thread overview]
Message-ID: <c20de38c-6671-a974-6e61-22a9e9177b71@embedded-brains.de> (raw)
In-Reply-To: <Ydws9XYIpU/DccD+@calimero.vinschen.de>
On 10/01/2022 13:56, Corinna Vinschen wrote:
>> The member access macros are incomplete. We would have to add macros for all
>> the struct _reent members. Would this be an approach acceptable for Newlib
>> integration?
> I think this would be acceptable, provided that the current
> implementation stays available.
The existing struct _reent implementation will be still the default.
Targets will get a new configuration option (for example
_REENT_THREAD_LOCAL) to use thread-local objects instead of members in a
structure. There will be several of new _REENT_XZY(ptr) macros to enable
this alternative implementation.
--
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/
next prev parent reply other threads:[~2022-01-10 16:26 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 [this message]
2022-05-19 8:49 ` Sebastian Huber
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=c20de38c-6671-a974-6e61-22a9e9177b71@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).