public inbox for newlib@sourceware.org
 help / color / mirror / Atom feed
From: Sebastian Huber <sebastian.huber@embedded-brains.de>
To: Newlib <newlib@sourceware.org>
Subject: Optionally use thread-local objects for struct _reent members
Date: Mon, 10 Jan 2022 10:28:52 +0100	[thread overview]
Message-ID: <32452837-4a35-d458-c971-c5c1e4f92290@embedded-brains.de> (raw)

Hello,

Newlib currently uses a huge object of type struct _reent to store 
thread-specific data. This object is returned by __getreent() if the 
__DYNAMIC_REENT__ Newlib configuration option is defined.

The reentrancy structure contains errno and also the standard input, 
output, and error file streams. This means that if an application only 
uses errno it has a dependency on the file stream support even if it 
does not use it. This is an issue for lower end targets and applications 
which need to qualify the software according to safety standards (for 
example ECSS-E-ST-40C, ECSS-Q-ST-80C, IEC 61508,
ISO 26262, DO-178, DO-330, DO-333).

One approach to disentangle the dependencies introduced by struct _reent 
is to get rid of this structure and replace the individual members of 
the structure with thread-local objects. For example, instead of

struct _reent {
   int _errno;
   __FILE *_stdin;
   __FILE *_stdout;
   __FILE *_stderr;
};

use

_Thread_local int _errno;
_Thread_local __FILE *_stdin;
_Thread_local __FILE *_stdout;
_Thread_local __FILE *_stderr;

if a new configuration option is defined (for example _REENT_THREAD_LOCAL).

Newlib already has access macros for some struct _reent members, for 
example:

#define _REENT_SIGNGAM(ptr)     ((ptr)->_new._reent._gamma_signgam)
#define _REENT_RAND_NEXT(ptr)   ((ptr)->_new._reent._rand_next)
#define _REENT_RAND48_SEED(ptr) ((ptr)->_new._reent._r48._seed)
#define _REENT_RAND48_MULT(ptr) ((ptr)->_new._reent._r48._mult)
#define _REENT_RAND48_ADD(ptr)  ((ptr)->_new._reent._r48._add)

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?

-- 
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/

             reply	other threads:[~2022-01-10  9:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-10  9:28 Sebastian Huber [this message]
2022-01-10 12:56 ` Corinna Vinschen
2022-01-10 16:26   ` Sebastian Huber
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=32452837-4a35-d458-c971-c5c1e4f92290@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).