From: Hans-Peter Nilsson <hp@axis.com>
To: Sebastian Huber <sebastian.huber@embedded-brains.de>
Cc: <newlib@sourceware.org>
Subject: Re: [PATCH] Fix stdio init handling
Date: Wed, 8 Jun 2022 01:30:13 +0200 [thread overview]
Message-ID: <20220607233013.542EC20417@pchp3.se.axis.com> (raw)
In-Reply-To: <5ee6a38c-d7f5-ed62-970d-b25aedee3a25@embedded-brains.de> (message from Sebastian Huber on Tue, 7 Jun 2022 08:18:49 +0200)
> From: Sebastian Huber <sebastian.huber@embedded-brains.de>
> Date: Tue, 7 Jun 2022 08:18:49 +0200
> sorry for breaking your Newlib configuration.
(A point I tried to make was that it wasn't just "mine", but
most "*-elf" ones. A "real" CI bot for a stable *-elf
simulator target with newlib, gcc, binutils, updating only
each at a time would be nice, and JFTR, no I don't consider
mine "real".)
> Could you please try the attached
> patch?
Aha; yes it works; I regtested gcc for cris-elf as with my
patch. Thanks for attending to this. I hope the other
points I raised in my submission will eventually be handled.
> We would like to introduce a configuration option for Newlib to use
> thread-local storage for the members of struct _reent:
>
> https://sourceware.org/pipermail/newlib/2022/018855.html
Ok, I see, thanks for clarifying.
> We also would like to make the _REENT_GLOBAL_STDIO_STREAMS option the
> default Newlib behaviour:
>
> https://sourceware.org/pipermail/newlib/2022/019735.html
Thanks; FWIW, I don't have a strong opinion about that. As
long as it still works, I'm happy. (Not actually using
newlib for production here, AFAIK.)
brgds, H-P
prev parent reply other threads:[~2022-06-07 23:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-06 18:20 Hans-Peter Nilsson
2022-06-06 20:16 ` Jeff Johnston
2022-06-07 6:21 ` Sebastian Huber
2022-06-07 14:47 ` Jeff Johnston
2022-06-07 6:05 ` Torbjorn SVENSSON
2022-06-07 14:40 ` Hans-Peter Nilsson
2022-06-07 6:18 ` Sebastian Huber
2022-06-07 19:31 ` Sebastian Huber
2022-06-07 23:30 ` Hans-Peter Nilsson [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=20220607233013.542EC20417@pchp3.se.axis.com \
--to=hp@axis.com \
--cc=newlib@sourceware.org \
--cc=sebastian.huber@embedded-brains.de \
/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).