public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gcc at abeckmann dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/33361] ICE in find_outermost_region_in_block, at tree-cfg.c:4803 Date: Sun, 09 Sep 2007 12:52:00 -0000 [thread overview] Message-ID: <20070909125159.1245.qmail@sourceware.org> (raw) In-Reply-To: <bug-33361-14599@http.gcc.gnu.org/bugzilla/> [-- Warning: decoded text below may be mangled, UTF-8 assumed --] [-- Attachment #1: Type: text/plain, Size: 1855 bytes --] ------- Comment #1 from gcc at abeckmann dot de 2007-09-09 12:51 ------- Created an attachment (id=14177) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=14177&action=view) testcase (reduced to be < 500k) Sorry for the delay of the testcase, I had to reduce it from 1.9 MB to 440 KB. (Is there some helper script that can do this in a more or less brute force way? Strip complete namespaces, classes, member functions, ... from the code, recompile and check for a certain error message? Continue it it's still there and backtrack otherwise?) $ /suse/NOBACKUP/gcc/gcc-4.2-branch/bin/g++ -v -march=i686 -O3 -fopenmp -c PR33361.ii Using built-in specs. Target: i686-pc-linux-gnu Configured with: ../gcc-4_2-branch/configure --enable-languages=c,c++ --prefix=/suse/NOBACKUP/gcc/gcc-4.2-branch Thread model: posix gcc version 4.2.2 20070908 (prerelease) /suse/NOBACKUP/gcc/gcc-4.2-branch/libexec/gcc/i686-pc-linux-gnu/4.2.2/cc1plus -fpreprocessed PR33361.ii -quiet -dumpbase PR33361.ii -march=i686 -auxbase PR33361 -O3 -version -fopenmp -o /tmp/ccslyrRU.s GNU C++ version 4.2.2 20070908 (prerelease) (i686-pc-linux-gnu) compiled by GNU C version 4.2.2 20070908 (prerelease). GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072 Compiler executable checksum: 7993b3af5142d87e347d8f7153b00978 PR33361.ii: In function Op mcstl::for_each_template_random_access_ed(RandomAccessIterator, RandomAccessIterator, Op, Fu&, Red, Result, Result&, typename std::iterator_traits<_Iterator>::difference_type) [with RandomAccessIterator = stxxl::request_ptr*, Op = stxxl::request_ptr, Fu = mcstl::fill_selector<stxxl::request_ptr*>, Red = mcstl::dummy_reduct, Result = bool]: PR33361.ii:3047: internal compiler error: in find_outermost_region_in_block, at tree-cfg.c:4803 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33361
next prev parent reply other threads:[~2007-09-09 12:52 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-09-09 0:13 [Bug c++/33361] New: " gcc at abeckmann dot de 2007-09-09 12:52 ` gcc at abeckmann dot de [this message] 2007-09-09 13:37 ` [Bug tree-optimization/33361] " rguenth at gcc dot gnu dot org 2007-09-09 13:41 ` rguenth at gcc dot gnu dot org 2007-09-09 14:24 ` rguenth at gcc dot gnu dot org 2007-09-09 14:25 ` rguenth at gcc dot gnu dot org 2007-09-17 17:36 ` gcc at abeckmann dot de 2007-12-27 16:04 ` reichelt at gcc dot gnu dot org 2008-03-10 10:29 ` jakub at gcc dot gnu dot org 2008-03-13 8:27 ` reichelt at gcc dot gnu dot org 2008-12-29 2:34 ` reichelt 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=20070909125159.1245.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: 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).