On Tuesday, May 24, 2011 08:02:50 PM Cristian Rodríguez wrote:
El 24/05/11 13:55, Andreas Jaeger escribió:
I've updated glibc from 2.11 to 2.13 for Base:System and like to see some testing: * Whether it runs fine on your system * Whether it breaks any package builds
Please tell me about any problems you encounter.
Does this release includes the "controversial" memcpy() optimization that has a huge potential of breaking (buggy|dubious|working) code ? (which one of the categories depends on language lawyers)
that was already disabled previously: Mon Nov 15 18:29:49 CET 2010 - pbaudis@suse.cz - Enable multi-arch routines support for ppc, ppc64, i686 and x86_64. Temporarily, AMD-optimized string routines are disabled. We will selectively re-enable them after some more careful benchmarking in the next few days. Note: In this glibc version, multi-arch routines DO NOT include the controversial backwards-copy memcpy() glibc 2.14 will have a solution for this... but let me double check whether this is really the case for my version or whether I introduced them again by accident. thanks, Andreas -- Andreas Jaeger, Program Manager openSUSE aj@{novell.com,suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org