On Wednesday 17 November 2010 22:59:54 Matthew Garrett wrote: > On Thu, Nov 18, 2010 at 12:42:56AM +0100, Kevin Kofler wrote: > > Because it's NOT a bug in glibc, because what glibc does is CORRECT, > > because it actually POINTS OUT bugs in applications which are > > portability issues and can hurt future optimization opportunities > > (regardless of whether the current implementation really is faster than > > before or not) and, most importantly, because it is NOT our job to work > > around bugs in proprietary software! > > Pretty sure it doesn't point them out. It just breaks them.
Using memcpy on overlapping ranges is undefined behavior; a crash is a pretty good way of pointing that out. Other undefined behavior causes a crash (last I checked): char*s = "Hi"; s[0] = 'h'; -- Ben -- Message sent on: Wed Nov 17 23:25:00 EST 2010
signature.asc
Description: This is a digitally signed message part.
-- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
