From: Sebastian Huber <sebastian.huber@embedded-brains.de>
To: newlib@sourceware.org
Subject: [PATCH 4/6] Optional struct _reent::_new::_unused
Date: Mon, 16 May 2022 08:55:55 +0200 [thread overview]
Message-ID: <20220516065557.78164-5-sebastian.huber@embedded-brains.de> (raw)
In-Reply-To: <20220516065557.78164-1-sebastian.huber@embedded-brains.de>
Provide struct _reent::_new::_unused only if _REENT_BACKWARD_BINARY_COMPAT is
defined.
---
newlib/libc/include/sys/reent.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/newlib/libc/include/sys/reent.h b/newlib/libc/include/sys/reent.h
index 5f557111e..1884ed982 100644
--- a/newlib/libc/include/sys/reent.h
+++ b/newlib/libc/include/sys/reent.h
@@ -687,6 +687,7 @@ struct _reent
_mbstate_t _wcsrtombs_state;
int _h_errno;
} _reent;
+#ifdef _REENT_BACKWARD_BINARY_COMPAT
/* Two next two fields were once used by malloc. They are no longer
used. They are used to preserve the space used before so as to
allow addition of new reent fields and keep binary compatibility. */
@@ -696,6 +697,7 @@ struct _reent
unsigned char * _nextf[_N_LISTS];
unsigned int _nmalloc[_N_LISTS];
} _unused;
+#endif
} _new;
# ifndef _REENT_GLOBAL_ATEXIT
--
2.35.3
next prev parent reply other threads:[~2022-05-16 6:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-16 6:55 [PATCH 0/6] Add --enable-newlib-reent-binary-compat configure option Sebastian Huber
2022-05-16 6:55 ` [PATCH 1/6] Add --enable-newlib-reent-binary-compat Sebastian Huber
2022-05-16 11:18 ` Corinna Vinschen
2022-05-16 11:54 ` Sebastian Huber
2022-05-16 6:55 ` [PATCH 2/6] Optional struct _reent::__unused_sdidinit Sebastian Huber
2022-05-16 6:55 ` [PATCH 3/6] Optional struct _reent::_unspecified_locale_info Sebastian Huber
2022-05-16 6:55 ` Sebastian Huber [this message]
2022-05-16 6:55 ` [PATCH 5/6] Optional struct _reent::_new::_reent::_unused_rand Sebastian Huber
2022-05-16 6:55 ` [PATCH 6/6] Use global atexit data for all configurations 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=20220516065557.78164-5-sebastian.huber@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).