2011/2/9 Ryan Hill <dirtye...@gentoo.org>
> On Tue, 08 Feb 2011 09:52:55 +0100
> "Paweł Hajdan, Jr." <phajdan...@gentoo.org> wrote:
>
> > It seems that with glibc-2.13 there are some serious compatibility
> > issues. There are good warnings on the planet
> > (http://psykil.livejournal.com/340806.html), but not every ~arch user
> > reads the planet, so how about creating news item with detailed
> > instructions how to ensure smooth glibc-2.13 update or recover a hosed
> > system?
>
> We've blocked prelink in the ebuild so if a user is able to sync they're
> either not going to be affected or already have been.
>
> Also I've the strong suspect that these changes:
* New optimized string functions for x86-64: strnlen (SSE2),
strcasecmp (SSE2, SSSE3, SSE4.2), strncasecmp (SSE2, SSSE3, SSE4.2)
Implemented by Ulrich Drepper.
Interact badly with strong optimizations like these
CFLAGS="-O2 -march=core2 -pipe"
CFLAGS="${CFLAGS} -msse4.1 --param l1-cache-size=32 --param
l1-cache-line-size=64 --param l2-cache-size=2048 -mtune=core2" # native
CFLAGS="${CFLAGS} -fgcse-after-reload -fpredictive-commoning
-ftree-vectorize -funswitch-loops" # O3 - -finline-functions -fipa-cp-clone
CFLAGS="${CFLAGS} -fgraphite-identity -floop-block -floop-interchange
-floop-strip-mine" # graphite & co (-fira-loop-pressure no good amd64)
using gcc-4.5.2
Since the upgrade I do get portage emerging text files .sh, .conf and such
as file of the exact same size but filled of \0, luckily most upgrade fails.
cpu is:
model name : Intel(R) Core(TM)2 Quad CPU Q8400 @ 2.66GHz
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm
constant_tsc arch_perfmon pebs bts rep_good nopl aperfmperf pni dtes64
monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave lahf_lm dts
tpr_shadow vnmi flexpriority
I've masked glibc-2.13, also I'm not filing a bug, because of non-usual
CFLAGS and because I'm not totally sure is glibc related.
