public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "Max dot Moorkamp at gmx dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/32950] New: -O1 and -O2 options cause internal compiler error Date: Tue, 31 Jul 2007 17:56:00 -0000 [thread overview] Message-ID: <bug-32950-14926@http.gcc.gnu.org/bugzilla/> (raw) [-- Warning: decoded text below may be mangled, UTF-8 assumed --] [-- Attachment #1: Type: text/plain, Size: 1737 bytes --] Hi, the -O1 and -O2 options cause an internal compiler error in my newly compiled g++ 4.2.1. Omitting this option compiles without any apparent problems and the ubuntu 06/10 g++, i.e. gcc version 4.1.2 20060928 (prerelease) (Ubuntu 4.1.1-13ubuntu5), also compiles it fine, with and without the -O2 or -O1. I still have the old g++ installed in the standard location. Here is the output of gcc -v Using built-in specs. Target: i486-linux-gnu Configured with: ../src/configure -v --enable-languages=c,c++,fortran,objc,obj-c++,treelang --prefix=/usr --enable-shared --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --enable-nls --program-suffix=-4.1 --enable-__cxa_atexit --enable-clocale=gnu --enable-libstdcxx-debug --enable-mpfr --enable-checking=release i486-linux-gnu Thread model: posix gcc version 4.1.2 20060928 (prerelease) (Ubuntu 4.1.1-13ubuntu5) my command line was /opt/gcc4.2.1/bin/g++-4.2 -O2 -c -save-temps bug2.cpp and produced this output bug2.cpp: In function int main(): bug2.cpp:16: internal compiler error: in convert_move, at expr.c:363 Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://gcc.gnu.org/bugs.html> for instructions. -- Summary: -O1 and -O2 options cause internal compiler error Product: gcc Version: 4.2.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: Max dot Moorkamp at gmx dot net GCC build triplet: i486-linux-gnu GCC host triplet: i486-linux-gnu GCC target triplet: i486-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32950
next reply other threads:[~2007-07-31 17:56 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-07-31 17:56 Max dot Moorkamp at gmx dot net [this message] 2007-07-31 17:57 ` [Bug c++/32950] " Max dot Moorkamp at gmx dot net 2007-07-31 18:06 ` [Bug middle-end/32950] " pinskia at gcc dot gnu dot org 2007-12-27 20:06 ` [Bug middle-end/32950] [4.1/4.2 regression] ICE with __complex__ double reichelt at gcc dot gnu dot org 2008-02-01 17:02 ` jsm28 at gcc dot gnu dot org 2008-05-19 20:28 ` jsm28 at gcc dot gnu dot org 2008-07-04 22:48 ` [Bug middle-end/32950] [4.2 " jsm28 at gcc dot gnu dot org 2009-03-30 22:12 ` jsm28 at gcc dot gnu dot org 2009-06-06 20:33 ` [Bug middle-end/32950] [4.5 " reichelt at gcc dot gnu dot org 2009-06-06 22:16 ` hjl dot tools at gmail dot com 2009-06-06 22:22 ` joseph at codesourcery dot com 2009-06-07 13:26 ` hjl dot tools at gmail dot com 2009-06-07 13:35 ` hjl at gcc dot gnu dot org 2009-06-07 13:39 ` hjl at gcc dot gnu dot org 2009-06-07 13:40 ` hjl at gcc dot gnu dot org 2009-06-07 14:42 ` jamborm at gcc dot gnu dot org 2009-06-07 15:55 ` pinskia at gcc dot gnu dot org 2009-06-08 17:49 ` jamborm at gcc dot gnu dot org 2009-06-08 17:51 ` pinskia at gcc dot gnu dot org 2009-06-12 23:17 ` sje at cup dot hp dot com 2009-06-17 15:41 ` sje at cup dot hp dot com
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=bug-32950-14926@http.gcc.gnu.org/bugzilla/ \ --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: linkBe 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).