public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/58380] New: ice in fold_comparison Date: Tue, 10 Sep 2013 10:21:00 -0000 [thread overview] Message-ID: <bug-58380-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58380 Bug ID: 58380 Summary: ice in fold_comparison Product: gcc Version: 4.9.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: dcb314 at hotmail dot com Created attachment 30785 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=30785&action=edit gzipped C++ source code I just tried to compile package k3d-0.8.0.2-19 with gcc 4.9 trunk dated 20130909. It said /home/dcb/rpmbuild/BUILD/k3d-source-0.8.0.2/k3dsdk/document_plugin_factory.h:48:9: internal compiler error: Segmentation fault inode* create_plugin(iplugin_factory& Factory, idocument& Document) ^ 0xacdd4f crash_signal ../../src/trunk/gcc/toplev.c:335 0x8b7709 fold_comparison ../../src/trunk/gcc/fold-const.c:9052 0x8c0b9b fold_binary_loc(unsigned int, tree_code, tree_node*, tree_node*, tree_node*) ../../src/trunk/gcc/fold-const.c:12780 0xaff5d2 cleanup_control_expr_graph ../../src/trunk/gcc/tree-cfgcleanup.c:96 0xaff5d2 cleanup_control_flow_bb ../../src/trunk/gcc/tree-cfgcleanup.c:171 0xaff5d2 cleanup_tree_cfg_bb ../../src/trunk/gcc/tree-cfgcleanup.c:589 0xb01018 cleanup_tree_cfg_1 ../../src/trunk/gcc/tree-cfgcleanup.c:634 0xb01018 cleanup_tree_cfg_noloop ../../src/trunk/gcc/tree-cfgcleanup.c:690 0xb01018 cleanup_tree_cfg() ../../src/trunk/gcc/tree-cfgcleanup.c:745 0xa27a84 execute_function_todo ../../src/trunk/gcc/passes.c:1791 0xa28167 execute_todo ../../src/trunk/gcc/passes.c:1866 Please submit a full bug report, with preprocessed source if appropriate. Please include the complete backtrace with any bug report. See <http://gcc.gnu.org/bugs.html> for instructions. Here is valgrind helping out with a stack backtrace ==23967== Invalid read of size 2 ==23967== at 0x8B7709: fold_comparison(unsigned int, tree_code, tree_node*, tree_node*, tree_node*) (fold-const.c:9052) ==23967== by 0x8C0B9B: fold_binary_loc(unsigned int, tree_code, tree_node*, tree_node*, tree_node*) (fold-const.c:12780) ==23967== by 0xAFF5D2: cleanup_tree_cfg_bb(basic_block_def*) (tree-cfgcleanup.c:96) ==23967== by 0xB01018: cleanup_tree_cfg() (tree-cfgcleanup.c:634) Preprocessed source code attached. Flag -O2 required.
next reply other threads:[~2013-09-10 10:21 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-09-10 10:21 dcb314 at hotmail dot com [this message] 2013-09-10 10:40 ` [Bug c++/58380] " mpolacek at gcc dot gnu.org 2013-09-10 12:45 ` [Bug c++/58380] [4.9 Regression] " mpolacek at gcc dot gnu.org 2013-09-10 13:32 ` [Bug tree-optimization/58380] " law at redhat dot com 2013-09-10 13:45 ` mpolacek at gcc dot gnu.org 2013-09-10 13:50 ` markus at trippelsdorf dot de 2013-09-10 14:04 ` rguenth at gcc dot gnu.org 2013-09-10 15:23 ` law at redhat dot com 2013-09-10 15:51 ` law at redhat dot com 2013-09-10 16:52 ` dcb314 at hotmail dot com 2013-09-11 2:23 ` law at gcc dot gnu.org 2013-09-11 2:31 ` law at redhat 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-58380-4@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).