public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "drab at kepler dot fjfi dot cvut dot cz" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/30565] New: ICE with -O1 -ftree-pre -ftree-loop-linear -funroll-loops Date: Tue, 23 Jan 2007 23:07:00 -0000 [thread overview] Message-ID: <bug-30565-8902@http.gcc.gnu.org/bugzilla/> (raw) [-- Warning: decoded text below may be mangled, UTF-8 assumed --] [-- Attachment #1: Type: text/plain, Size: 2276 bytes --] Hi, the attached code, when compiled with the following gcc: -------------------------------- $ gcc -v Using built-in specs. Target: i686-pc-linux-gnu Configured with: ../../../gcc-SVN-20070121/gcc-SVN-20070121/configure --prefix=/usr/local/MDLinux/opt/gcc-4.3 --exec-prefix=/usr/local/MDLinux/opt/gcc-4.3 --sysconfdir=/etc --libdir=/usr/local/MDLinux/opt/gcc-4.3/lib --libexecdir=/usr/local/MDLinux/opt/gcc-4.3/libexec --sharedstatedir=/var --localstatedir=/var --program-suffix=-4.3 --with-x-includes=/usr/X11R6/include --with-x-libraries=/usr/X11R6/lib --enable-shared --enable-static --with-gnu-as --with-gnu-ld --with-stabs --enable-threads=posix --enable-version-specific-runtime-libs --disable-werror --enable-tls --disable-coverage --disable-libgcj --disable-checking --enable-multilib --with-x --enable-cmath --enable-libstdcxx-debug --enable-fast-character --enable-hash-synchronization --with-system-zlib --with-libbanshee --with-demangler-in-ld --disable-rpath --with-arch=athlon-xp --disable-libada --enable-languages=c,c++,fortran Thread model: posix gcc version 4.3.0 20070121 (experimental) -------------------------------- using following command line: -------------------------------- gcc -O1 -ftree-pre -ftree-loop-linear -funroll-loops -c psycho_n1.c -o psycho_n1.o -------------------------------- ICEs like this: -------------------------------- psycho_n1.c: In function âpsycho_n1â: psycho_n1.c:64: internal compiler error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://gcc.gnu.org/bugs.html> for instructions. -------------------------------- Removal of any of the optimizing flags makes it compile. Tested on i686. -- Summary: ICE with -O1 -ftree-pre -ftree-loop-linear -funroll- loops Product: gcc Version: 4.3.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: drab at kepler dot fjfi dot cvut dot cz GCC build triplet: i686-pc-linux-gnu GCC host triplet: i686-pc-linux-gnu GCC target triplet: i686-pc-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30565
next reply other threads:[~2007-01-23 23:07 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-01-23 23:07 drab at kepler dot fjfi dot cvut dot cz [this message] 2007-01-23 23:09 ` [Bug tree-optimization/30565] " drab at kepler dot fjfi dot cvut dot cz 2007-01-23 23:34 ` drab at kepler dot fjfi dot cvut dot cz 2007-04-30 9:18 ` [Bug tree-optimization/30565] ICE with -O1 -ftree-pre -ftree-loop-linear rguenth at gcc dot gnu dot org 2007-04-30 17:42 ` dberlin at dberlin dot org 2007-05-02 21:15 ` rakdver at gcc dot gnu dot org 2007-05-03 13:27 ` rakdver at gcc dot gnu dot org 2007-05-06 23:09 ` pinskia at gcc dot gnu dot org 2007-10-01 15:15 ` pthaugen at gcc dot gnu dot org
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-30565-8902@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).