Am 05.05.2010 02:46, schrieb Allan McRae:
Now I noticed the exact same issue with busybox: - Building with -Os throws lots of aliasing warnings, busybox's sed breaks - Building with -Os -fno-strict-aliasing builds without warnings, but it still breaks. - Building with -O0 works, but it isn't optimal.
Interesting... Does fixing the aliasing fix this one too? I see no upstream bug reports that seem related so you should follow it up there. I will pull in a new gcc-4.5 snapshot next week when I do the glibc-2.12 toolchain rebuild so hopefully that may contain a fix that I am missing...
I can only guess. You can remove -fno-strict-aliasing from the mkinitcpio-busybox PKGBUILD and build, then count the number of warnings - there's hundreds. I opened an upstream bug report, but I was so far unable to produce a test case they can use.