From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8401 invoked by alias); 21 Apr 2010 13:43:17 -0000 Received: (qmail 8208 invoked by uid 48); 21 Apr 2010 13:42:55 -0000 Date: Wed, 21 Apr 2010 13:43:00 -0000 Message-ID: <20100421134255.8207.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug c++/43818] internal compiler error: Segmentation fault In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "oberlaender at fzi dot de" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2010-04/txt/msg02185.txt.bz2 ------- Comment #8 from oberlaender at fzi dot de 2010-04-21 13:42 ------- Just tested 4.5.0, which did not crash. $ g++-4.5.0 -c -o bugtest.out -O2 bugtest.ii $ g++-4.5.0 -v Using built-in specs. COLLECT_GCC=g++-4.5.0 COLLECT_LTO_WRAPPER=/home/oberlaen/local/stow/gcc-4.5.0/libexec/gcc/i486-linux-gnu/4.5.0/lto-wrapper Target: i486-linux-gnu Configured with: ../gcc-4.5.0/configure --prefix=/home/oberlaen/local/stow/gcc-4.5.0/ --with-bugurl=file:///usr/share/doc/gcc-4.5/README.Bugs --enable-languages=c,c++ --enable-shared --disable-multiarch --enable-linker-build-id --with-system-zlib --without-included-gettext --enable-threads=posix --program-suffix=-4.5.0 --enable-nls --enable-clocale=gnu --enable-libstdcxx-debug --enable-objc-gc --enable-targets=all --disable-multilib --disable-werror --with-arch-32=i486 --with-tune=generic --enable-checking=release --build=i486-linux-gnu --host=i486-linux-gnu --target=i486-linux-gnu --with-mpc=/home/oberlaen/local Thread model: posix gcc version 4.5.0 (GCC) Also, all the 4.4.x versions work fine if I replace -O2 with -O1. The question remains, what is going wrong with my various 4.4.x tests, and why did it work for Jonathan? I've circumvented the problem in my piece of software for now by going from -O2 to -O1, as I don't feel like rebuilding everything against 4.5 just yet. :) But at least according to my tests, the problem is present in all 4.4 releases. Can anyone else reproduce the error? Thanks and best regards, Jan -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43818