From: Roland McGrath <roland@redhat.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Ulrich Drepper <drepper@redhat.com>,
GNU libc hackers <libc-hacker@sources.redhat.com>
Subject: Re: BUGS file
Date: Fri, 02 Jul 2004 05:52:00 -0000 [thread overview]
Message-ID: <200407020552.i625q2ep021386@magilla.sf.frob.com> (raw)
In-Reply-To: Jakub Jelinek's message of Wednesday, 30 June 2004 08:24:21 +0200 <20040630062421.GU5191@sunsite.ms.mff.cuni.cz>
> And update the bugreporting instructions in there:
Yeah, http://sources.redhat.com/bugzilla/show_bug.cgi?id=234 is about this.
That's what motivated me to look at the file. It all looks so stale that
rather than just update those instructions I thought about nuking the file.
Can we verify now which of these items still applies?
[ **] Closing shared objects in statically linked binaries most of the
times leads to crashes during the dlopen(). Hard to fix.
Don't know.
[ **] There are problems with signal handling when using LinuxThreads.
Not planning to fix this, since we have NPTL now.
[ **] The RPC code is not 64 bit clean. This is getting slowly fixed
but expect incompatible changes on 64 bit platforms like Alpha.
I think this may now be as fixed as it's going to get.
[ **] If a DSO is using implicitly libpthread and the application itself
does not there is a name lookup problem. E.g., the function fork()
will be found in the libc.so instead of libpthread since the thread
library is behind the libc. To correct this problem it must *not*
be relied on the currently still enabled handling of weak symbols
in the dynamic linker. Instead explicit tests for the availability
of the libpthread version are needed. [PR libc/2325]
I don't think this is a problem any more, since those functions that are
duplicated between libc and libpthread now always forward to their counterpart.
[ *] The precision of the `sinhl' and/or `asinhl' function do not seem
to be the best.
[ *] The libm-ieee `gamma' function gives wrong results (at least for
-0.5).
[ *] The libm-ieee `scalb' function gives wrong results for
non-integral second parameters.
I don't know the status of these, though libm has had various changes in
the last two years since BUGS was updated.
[ *] On Linux, there should be a way to prevent defining the symbol
NGROUPS_MAX in the <linux/limits.h> header file. In glibc it
is defined in <posix1_lim.h> which must not make the other
symbols in <linux/limits.h> available.
[PR libc/140]
This is still the case. But it's really something that needs to be changed
in the installed <linux/limits.h> kernel header, and then libc will do the
right thing.
[ *] Several (most?) collation specifications are broken.
I don't know anything about this stuff.
[ *] Some of the functions which also handled IPv6 are currently broken.
IPv6 and IPv4 lookups occasionally happen when not needed. This
happens in getaddrinfo() and getnameinfo(). IPv4 handling of
these functions is OK though and there are patches available to fix
the IPv6 code as well.
I believe this is fixed now. If anything remains to do here, it should
have an active bugzilla report since it's something we don't want to have
slide forever.
Thanks,
Roland
prev parent reply other threads:[~2004-07-02 5:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-28 6:26 Roland McGrath
2004-06-28 20:48 ` Ulrich Drepper
2004-06-28 23:16 ` Roland McGrath
2004-06-28 23:25 ` Ulrich Drepper
2004-06-28 23:34 ` Roland McGrath
2004-06-30 8:39 ` Jakub Jelinek
2004-07-02 5:52 ` Roland McGrath [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=200407020552.i625q2ep021386@magilla.sf.frob.com \
--to=roland@redhat.com \
--cc=drepper@redhat.com \
--cc=jakub@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).