ftree-loop-linear breaks kdelibs. Might be an idea to filter ftree-loop-linear when compiling with gcc 4.2. Reproducible: Always Steps to Reproduce: 1. Add ftree-loop-linear to CFLAGS 2. Compile kdelibs 3. Try to run, say, Konqueror. Actual Results: Konqueror segfaults. kbuildsycoca running... KCrash: Application 'konqueror' crashing... Expected Results: Konqueror shouldn't crash. kbuildsycoca running... [New Thread 0x2b5671798530 (LWP 13935)] (no debugging symbols found) Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x2b5671798530 (LWP 13935)] 0x00002b566a7514de in memcpy () from /lib/libc.so.6 I'm guessing something like: #-ftree-loop-linear with 4.2.* breaks kdelibs 3.3.8 if gcc-version ge 4 2 && gcc-version lt 4 3; then filter-flags -ftree-loop-linear fi Should ideally be added to the ebuild.
Did you try to recompile qt, kdelibs and each of those programs before trying to run it? Did those errors appear after upgrading to gcc without rebuilding both qt, kdelibs and the kde programs?
No, I didn't. I just removed ftree-loop-linear, recompiled and it worked again. Then I recompiled again with ftree-loop-linear and it didn't work. Finally, I compiled it without again. Then it worked. Do programmes with ftree-loop-linear sometimes not work if dependencies aren't compiled with the same flag? If so I guess I could try compiling it with loop-linear again and kdebase as well...
It is not a supported compiler flag, so there's no point in filtering it, but maybe the toolchain team is interested, especially, if you can provide a reduced test case. gcc bugzilla shows up some issues, too: http://tinyurl.com/3aoyo5
Okay, I just thought you might want to filter it. I've never actually experienced a miscompilation with the flag before, just ICEs. As for a reduced testcase, I sincerely doubt that, my apologies but I'm quite new to the non-Windows world (thus have no experience debugging). Just your average layman, yada yada.
gcc-4.2.3 is in the tree if you want to re-test ... it'd be good to get a reduced test case here
I can't reproduce this with gcc-4.3.
