| |||||||||||||
Changes in glibc developmentChanges in glibc developmentPosted Mar 28, 2012 5:40 UTC (Wed) by cmccabe (guest, #60281)Parent article: Changes in glibc development
With Ulrich gone, where will we get our drama from?
Who will break Flash for everyone by changing memcpy to not work with overlapping regions? Who will force everyone to write their own wrapper for gettid() on Linux (despite the fact that glibc has several interfaces that require the result of gettid to be passed to them).
Who will declare that "tarballs are obsolete" and force everyone to fetch his releases from (the completely non-obsolete) CVS system? Who else will try to rip out sunRPC from glibc before there's an alternate working implementation? Who else will refuse to make setenv thread-safe, because programmers who don't read the fine print of POSIX need to get burned (and obviously setenv is such a performance bottleneck.)
With Ulrich gone, I can only imagine that glibc is going to be positively boring...
(Log in to post comments)
Changes in glibc development Posted Mar 28, 2012 7:03 UTC (Wed) by quotemstr (subscriber, #45331) [Link]
> Who will break Flash for everyone by changing memcpy to not work with overlapping regions?
Yet again: memcpy isn't guaranteed to work on overlapping regions. Use memmove if you think regions might overlap. Whatever else Drepper did, changing memcpy was perfectly legitimate.
Changes in glibc development Posted Mar 28, 2012 16:58 UTC (Wed) by cmccabe (guest, #60281) [Link]
Linus Torvalds believed that the new memcpy was actually slower, as well as a bad decision from the release management point of view. There's no point in rehashing the discussion, you can find it all here:
https://bugzilla.redhat.com/show_bug.cgi?id=638477
Changes in glibc development Posted Mar 28, 2012 7:21 UTC (Wed) by suckfish (guest, #69919) [Link]
Sounds like you're looking for Solaris, not Linux. In Solaris land, anything goes (most of the time). Bogus memcpy doesn't crash (most of the time). Bogus free doesn't crash (most of the time).
Good for design wins for marketing droids selling to corporates --- "look, your crappy code compiles and runs (most of the time)".
Crap for anyone who actually wants bugs to get fixed.
Changes in glibc development Posted Mar 28, 2012 8:46 UTC (Wed) by jengelh (subscriber, #33263) [Link]
>Good for design wins for marketing droids selling to corporates --- "look, your crappy code compiles and runs (most of the time)". Crap for anyone who actually wants bugs to get fixed.
The x86 architecture is just the same (and so are others like IA64).
Changes in glibc development Posted Mar 28, 2012 10:45 UTC (Wed) by dps (subscriber, #5725) [Link]
Having used Solaris (SPARC) I know in that land newly allocated memory frequently contains values very different from 0 which can break *buggy* code that allocates an array of pointers on the heap and assumes they are all initially null. This usually just works on Linux.
Solaris has not monopoly on "your bugware just works most of the time". Some bugware dies badly on Solaris but works on Linux and other systems where freshly allocated memory is all 0 most of the time.
What I really don't like in glibc is implementing a pipe2 function returning ENOSYS, if is not implemented, instead of implementing it using pipe(2) and fcntl(2), No doubt someone would call this is a feature but I can't work up enough enthusiasm for it to do so.
Changes in glibc development Posted Mar 28, 2012 11:42 UTC (Wed) by mpr22 (subscriber, #60784) [Link] It's not that returning ENOSYS is a feature, but that pretending to work would be a hidden-race-condition bug.
Changes in glibc development Posted Mar 28, 2012 12:59 UTC (Wed) by man_ls (subscriber, #15091) [Link] With Ulrich gone, where will we get our drama from?You can always install OpenBSD and follow de Raadt. Or you can <shiver>buy a TV set<shiver>.
Changes in glibc development Posted Aug 22, 2012 9:15 UTC (Wed) by arekm (subscriber, #4846) [Link]
.. or Miller on netdev. Similar attitude recently.
Changes in glibc development Posted Aug 22, 2012 13:44 UTC (Wed) by nix (subscriber, #2304) [Link]
Your comment is unintentionally ironic, since Uli and davem really *really* didn't get on. (I also note that davem will at least listen to reasoned argument.)
Changes in glibc development Posted Mar 28, 2012 18:16 UTC (Wed) by nix (subscriber, #2304) [Link] Who will break Flash for everyone by changing memcpy to not work with overlapping regions?That optimization was due to H. J. Lu, who is still involved. :)
|
|||||||||||||