public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "paulo@matos-sorge.com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/58463] New: ICE with -fdump-tree-all-all in vector indexed access Date: Wed, 18 Sep 2013 15:12:00 -0000 [thread overview] Message-ID: <bug-58463-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58463 Bug ID: 58463 Summary: ICE with -fdump-tree-all-all in vector indexed access Product: gcc Version: 4.8.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: middle-end Assignee: unassigned at gcc dot gnu.org Reporter: paulo@matos-sorge.com Created attachment 30855 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=30855&action=edit Code example to reproduce ICE GCC tries to access varmap through get_varinfo in tree-ssa-structalias.c, but it fails with an ICE. I have attached a reduced code example to reproduce the problem. The command line and output with 4.8.1 is: $ ~/work/tmp/gcc-4.8.1/gcc/cc1 -fpreprocessed -fdump-tree-all-all -O2 core_list_join.i core_list_join.i:4:1: warning: no semicolon at end of struct or union [enabled by default] } ^ fn1 Analyzing compilation unit Performing interprocedural optimizations <*free_lang_data> <visibility> <early_local_cleanups> core_list_join.i: In function 'fn1': core_list_join.i:9:1: internal compiler error: in operator[], at vec.h:815 } ^ 0xbfd572 vec<variable_info*, va_heap, vl_embed>::operator[](unsigned int) /home/pmatos/work/gcc-releases/gcc-4.8.1/gcc/vec.h:815 0xbfcea0 vec<variable_info*, va_heap, vl_ptr>::operator[](unsigned int) /home/pmatos/work/gcc-releases/gcc-4.8.1/gcc/vec.h:1244 0xbeb5ba get_varinfo /home/pmatos/work/gcc-releases/gcc-4.8.1/gcc/tree-ssa-structalias.c:319 0xbefa59 perform_var_substitution /home/pmatos/work/gcc-releases/gcc-4.8.1/gcc/tree-ssa-structalias.c:2244 0xbfb279 solve_constraints /home/pmatos/work/gcc-releases/gcc-4.8.1/gcc/tree-ssa-structalias.c:6569 0xbfb679 compute_points_to_sets /home/pmatos/work/gcc-releases/gcc-4.8.1/gcc/tree-ssa-structalias.c:6665 0xbfbdca compute_may_aliases() /home/pmatos/work/gcc-releases/gcc-4.8.1/gcc/tree-ssa-structalias.c:6814 0x967b9e execute_function_todo /home/pmatos/work/gcc-releases/gcc-4.8.1/gcc/passes.c:1941 0x966f88 do_per_function /home/pmatos/work/gcc-releases/gcc-4.8.1/gcc/passes.c:1701 0x967d64 execute_todo /home/pmatos/work/gcc-releases/gcc-4.8.1/gcc/passes.c:1996 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.
next reply other threads:[~2013-09-18 15:12 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-09-18 15:12 paulo@matos-sorge.com [this message] 2013-09-19 16:37 ` [Bug middle-end/58463] " mpolacek at gcc dot gnu.org 2013-09-20 7:50 ` rguenth at gcc dot gnu.org 2013-09-20 8:51 ` paulo@matos-sorge.com 2013-09-20 9:00 ` paulo@matos-sorge.com 2013-09-20 10:07 ` rguenther at suse dot de 2013-09-20 10:29 ` paulo@matos-sorge.com 2013-09-27 14:54 ` pmatos at gcc dot gnu.org 2013-09-27 16:30 ` [Bug tree-optimization/58463] " pmatos at gcc dot gnu.org 2013-09-27 16:44 ` [Bug middle-end/58463] " pmatos at gcc dot gnu.org 2013-09-27 16:46 ` paulo@matos-sorge.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-58463-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).