From: Roland McGrath <roland@frob.com>
To: drepper@redhat.com (Ulrich Drepper)
Cc: GNU libc hacker <libc-hacker@sources.redhat.com>
Subject: Re: __libc_subinit
Date: Sat, 23 Feb 2002 17:51:00 -0000 [thread overview]
Message-ID: <20020224015140.06DCD1BA14@perdition.linnaean.org> (raw)
In-Reply-To: Ulrich Drepper's message of , 23 February 2002 00:57:05 -0800 <m3r8ncr2xq.fsf@myware.mynet>
> I've just removed the handling of __libc_subinit completely from the
> Linux setup. It really was only an expensive way to call a single
> function. This is now done directly instead.
It's not that expensive. And it was a way to call either zero or one
functions for static linking (i.e. if you didn't use __progname, zero).
But I am not going to argue.
How about you just rename __init_misc to __libc_init instead of diddling
every init-first.c file (and you missed some)?
> One, the stdio initialization, will eventually go away.
Indeed it will.
> This leave the use in times.c.
I don't mind changing that one.
next prev parent reply other threads:[~2002-02-24 1:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-23 0:57 __libc_subinit Ulrich Drepper
2002-02-23 17:51 ` Roland McGrath [this message]
2002-02-23 17:57 ` __libc_subinit Ulrich Drepper
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=20020224015140.06DCD1BA14@perdition.linnaean.org \
--to=roland@frob.com \
--cc=drepper@redhat.com \
--cc=libc-hacker@sources.redhat.com \
/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).