2009/10/16 Michael Matz <matz(a)suse.de>de>:
On Thu, 15 Oct 2009, Cristian Morales Vega wrote:
so many of the functions turn out to do the same thing
perhaps it would be worthwhile if somebody looked at each of the
common ones to determine where real differences are left to explain
the dead-locks we see occasionally. Perhaps we can get rid of them by
some small extensions in glibc.
I have unpacked glibc sources and... I'm scared :-p (being unable to
easily install kscope because of some stupid dependency issues doesn't
You don't want to look at the glibc sources to initially determine this.
It's non-trivial to determine which source files are actually compiled
into glibc depending on the configuration, and which headers are actually
used to define some of the macros used in sources (that can expand to
different things, again depending on configuration). For differences I
looked at the dis-assembly of the functions in question. The list of
double symbols that possibly matter is below. Some of the symbols are
just aliases to each other. And after looking at the asm differences (or
non-differences) I referred back to the sources to see if that made sense.
Sorry, my assembly knowledge is near zero. I even tried looking at
open(), but I would have said libc and libpthread implementations are
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org