From: Corinna Vinschen <vinschen@redhat.com>
To: newlib@sourceware.org
Subject: Re: [PATCH] Delete default __getreent() implementation
Date: Wed, 08 Nov 2017 16:34:00 -0000 [thread overview]
Message-ID: <20171108111603.GC24901@calimero.vinschen.de> (raw)
In-Reply-To: <484021594.8830.1510082305768.JavaMail.zimbra@embedded-brains.de>
[-- Attachment #1: Type: text/plain, Size: 1646 bytes --]
On Nov 7 20:18, Sebastian Huber wrote:
>
>
> ----- Am 7. Nov 2017 um 17:12 schrieb Craig Howland howland@LGSInnovations.com:
>
> > On 11/07/2017 10:03 AM, Corinna Vinschen wrote:
> >> On Nov 7 12:53, Sebastian Huber wrote:
> [...]
> > I suggest that at a minimum the contents of getreent.c should be kept. This
> > keeps a starting point for people who are needing to supply such a function.
>
> The default implementation is a bad example. It makes no sense to use __DYNAMIC_REENT__ with this implementation, e.g. you get the same thing without a function call overhead:
>
> #if defined(__DYNAMIC_REENT__) && !defined(__SINGLE_THREAD__)
> #ifndef __getreent
> struct _reent * _EXFUN(__getreent, (void));
> #endif
> # define _REENT (__getreent())
> #else /* __SINGLE_THREAD__ || !__DYNAMIC_REENT__ */
> # define _REENT _impure_ptr
> #endif /* __SINGLE_THREAD__ || !__DYNAMIC_REENT__ *
>
> > (Leaving it out of the library stops the link problem which is the stated goal
> > of the patch.) But I think it needs to go further, and this patch should not be
> > done in this form because of the cited backwards-compatibility reasons. If
> > something were to be done it should be a configure flag to leave it out of the
> > library.
>
> Then we are back to Joel's patch:
>
> https://sourceware.org/ml/newlib/2017/msg01026.html
>
> I don't know why Joel added this _dummy_getreent, but something similar is used elsewhere:
The "I don't know" is the key here. And as long as Joel doesn't
answer this question, this is on hold.
Corinna
--
Corinna Vinschen
Cygwin Maintainer
Red Hat
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2017-11-08 11:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-07 11:56 Sebastian Huber
2017-11-07 12:54 ` Sebastian Huber
2017-11-07 16:12 ` Corinna Vinschen
2017-11-07 16:19 ` Craig Howland
2017-11-07 16:39 ` Corinna Vinschen
2017-11-07 19:37 ` Sebastian Huber
2017-11-08 16:34 ` Corinna Vinschen [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=20171108111603.GC24901@calimero.vinschen.de \
--to=vinschen@redhat.com \
--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).