http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49034
--- Comment #2 from Michael Brown <michaelatnavman at gmail dot com> 2011-05-23 06:38:35 UTC --- Based on previous experiences, it'll be at least a couple of weeks to bring up a similarly configured (cross-compiling darwin-x86 -> arm-eabi) FSF toolchain. The command line is (paths and project-specific defines removed for clarity, but otherwise unchanged): arm-linux-androideabi-g++ -MMD -MP -MF foo.o.d.org -fpic -ffunction-sections -funwind-tables -fstack-protector -D__ARM_ARCH_5__ -D__ARM_ARCH_5T__ -D__ARM_ARCH_5E__ -D__ARM_ARCH_5TE__ -Wno-psabi -march=armv5te -mtune=xscale -msoft-float -fno-exceptions -fno-rtti -mthumb -Os -fomit-frame-pointer -fno-strict-aliasing -finline-limit=64 -Wa,--noexecstack -fexceptions -frtti -O2 -DNDEBUG -g -fexceptions -frtti -c foo.cpp -o foo.o Yes, it's asking for no exceptions and no RTTI, and also for them to be enabled. The wondrous inflexibilities of the android NDK ... Preprocessed output is several MB, and I'm probably not allowed to post it anyhow. Given how sensitive the bug is to surrounding code (changing only peripherally related code causes the bug to vanish) it'll probably take another couple of weeks (after getting the toolchain going) to get a decent test case going. As mentioned in the initial report, I don't really expect this to be fixed. It's just to let people who are seeing bizarre or "impossible" SIGSEGV exceptions a hint as to where to look. Given: (a) the amount of work required to get a satisfactory bug report together is large, and (b) a workaround exists (turn off optimization), and (b) no-one else seems to have run into this, and (c) the bug is in a GCC version that was released two years ago, and (d) the likelihood that due to the sensitivity of the bug to the surrounding code, other unrelated changes in GCC will result in the test case failing to tickle the bug in later versions even if the bug still being present, it ends up on the pile of things that get worked on in the evenings when I have time. Hence why it'll probably be a month if not longer before I can get a useful test case together.
