Am 05.05.2010 00:23, schrieb Thomas Bächler:
I noticed problem with gcc 4.5 and the GAP system (http://www.gap-system.org) first: It throws a few aliasing warnings, and the program breaks. When I used -fno-strict-aliasing, the warnings disappeared, but the breakage remained, unless I used -O0. Fixing the aliasing problems also fixed the breakage.
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.
This will affect LOTS of other programs and these errors will not show up as errors or warnings during the build procedure.
I am now building busybox with -O0 again, as '-Os -fno-strict-aliasing -fno-tree-pta' seemed to work at first, but it turned out the 'sed' output from busybox was just a few unreadable characters. I tested -O0 and it fixes the problems, but the binary is way too large. Btw, why do I always get signoffs, then move it, and only then get these reports?