public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "oberlaender at fzi dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/43818] internal compiler error: Segmentation fault
Date: Wed, 21 Apr 2010 13:43:00 -0000	[thread overview]
Message-ID: <20100421134255.8207.qmail@sourceware.org> (raw)
In-Reply-To: <bug-43818-19063@http.gcc.gnu.org/bugzilla/>



------- 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


  parent reply	other threads:[~2010-04-21 13:43 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-20 14:06 [Bug c++/43818] New: " oberlaender at fzi dot de
2010-04-20 14:09 ` [Bug c++/43818] " oberlaender at fzi dot de
2010-04-20 14:14 ` oberlaender at fzi dot de
2010-04-20 15:29 ` oberlaender at fzi dot de
2010-04-20 16:27 ` redi at gcc dot gnu dot org
2010-04-20 16:51 ` oberlaender at fzi dot de
2010-04-21 11:48 ` oberlaender at fzi dot de
2010-04-21 12:40 ` oberlaender at fzi dot de
2010-04-21 13:43 ` oberlaender at fzi dot de [this message]
2010-04-21 16:24 ` redi at gcc dot gnu dot org
2010-04-22  7:47 ` oberlaender at fzi dot de
2010-04-22  7:59 ` oberlaender at fzi dot de
2010-04-22  8:31 ` oberlaender at fzi dot de
2010-04-22  9:13 ` oberlaender at fzi dot de
2010-04-22  9:19 ` oberlaender at fzi dot de
2010-04-22 10:50 ` redi at gcc dot gnu dot org
2010-04-22 11:25 ` rguenth at gcc dot gnu dot org
2010-04-22 15:49 ` oberlaender at fzi dot de
2010-04-23 14:53 ` oberlaender at fzi dot de

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100421134255.8207.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).