public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "zsojka at seznam dot cz" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/59670] New: ICE: expected gimple_call(error_mark), have gimple_assign(plus_expr) in gimple_call_internal_p, at gimple.h:2432 Date: Fri, 03 Jan 2014 21:31:00 -0000 [thread overview] Message-ID: <bug-59670-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59670 Bug ID: 59670 Summary: ICE: expected gimple_call(error_mark), have gimple_assign(plus_expr) in gimple_call_internal_p, at gimple.h:2432 Product: gcc Version: 4.9.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: middle-end Assignee: unassigned at gcc dot gnu.org Reporter: zsojka at seznam dot cz Created attachment 31568 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=31568&action=edit reduced testcase Compiler output: $ gcc -O -fopenmp testcase.c testcase.c: In function 'foo': testcase.c:4:1: internal compiler error: gimple check: expected gimple_call(error_mark), have gimple_assign(plus_expr) in gimple_call_internal_p, at gimple.h:2432 foo (int j, int b) ^ 0x90792c gimple_check_failed(gimple_statement_base const*, char const*, int, char const*, gimple_code, tree_code) /mnt/svn/gcc-trunk/gcc/gimple.c:1132 0x62b077 gimple_call_internal_p /mnt/svn/gcc-trunk/gcc/gimple.h:2432 0x1409ded gimple_call_internal_p /mnt/svn/gcc-trunk/gcc/tree-vect-data-refs.c:3328 0x1409ded vect_analyze_data_refs(_loop_vec_info*, _bb_vec_info*, int*) /mnt/svn/gcc-trunk/gcc/tree-vect-data-refs.c:3323 0xd347a7 vect_analyze_loop_2 /mnt/svn/gcc-trunk/gcc/tree-vect-loop.c:1636 0xd347a7 vect_analyze_loop(loop*) /mnt/svn/gcc-trunk/gcc/tree-vect-loop.c:1846 0xd4b6c8 vectorize_loops() /mnt/svn/gcc-trunk/gcc/tree-vectorizer.c:430 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. $ gcc -v Using built-in specs. COLLECT_GCC=/mnt/svn/gcc-trunk/binary-latest/bin/gcc COLLECT_LTO_WRAPPER=/mnt/svn/gcc-trunk/binary-206310-lto-fortran-checking-yes-rtl-df/libexec/gcc/x86_64-unknown-linux-gnu/4.9.0/lto-wrapper Target: x86_64-unknown-linux-gnu Configured with: /mnt/svn/gcc-trunk//configure --enable-checking=yes,rtl,df --enable-languages=c,c++,lto,fortran --prefix=/mnt/svn/gcc-trunk/binary-206310-lto-fortran-checking-yes-rtl-df/ --without-cloog --without-ppl Thread model: posix gcc version 4.9.0 20140103 (experimental) (GCC) Tested revisions: r206310 - crash 4.8 - ignoring #pragma omp simd
next reply other threads:[~2014-01-03 21:31 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-01-03 21:31 zsojka at seznam dot cz [this message] 2014-01-07 11:29 ` [Bug middle-end/59670] " rguenth at gcc dot gnu.org 2014-01-07 11:32 ` jakub at gcc dot gnu.org 2014-01-09 23:39 ` jakub at gcc dot gnu.org 2014-01-09 23:42 ` jakub at gcc dot gnu.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-59670-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).