public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gang.chen.5i5j at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/66620] New: bfin: bfin.c: (hwloop_optimize): gcc_assert (JUMP_P (insn)) fails. Date: Mon, 22 Jun 2015 01:54:00 -0000 [thread overview] Message-ID: <bug-66620-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66620 Bug ID: 66620 Summary: bfin: bfin.c: (hwloop_optimize): gcc_assert (JUMP_P (insn)) fails. Product: gcc Version: 6.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: gang.chen.5i5j at gmail dot com Target Milestone: --- [root@localhost gcc]# cat lpt_commit.i struct ubifs_nnode { int iip; int level; int nbranch[4]; }; struct ubifs_nnode *next_pnode_to_dirty(struct ubifs_nnode *nnode) { int iip; while (nnode->level > 1) { for (iip = 0; iip < 4; iip++) { if (nnode->nbranch[iip]) break; } nnode = nnode + iip; } for (iip = 0; iip < 4; iip++) if (nnode->nbranch[iip]) break; return nnode + iip; } [root@localhost gcc]# /upstream/build-gcc-blackfin/gcc/cc1 -Os -fno-reorder-blocks lpt_commit.i next_pnode_to_dirty Analyzing compilation unit Performing interprocedural optimizations <*free_lang_data> <visibility> <build_ssa_passes> <opt_local_passes> <free-inline-summary> <emutls> <whole-program> <profile_estimate> <icf> <devirt> <cp> <inline> <pure-const> <static-var> <single-use> <comdats>Assembling functions: next_pnode_to_dirty lpt_commit.i: In function 'next_pnode_to_dirty': lpt_commit.i:24:1: internal compiler error: in hwloop_optimize, at config/bfin/bfin.c:3523 } ^ 0xd9c8eb hwloop_optimize ../../gcc/gcc/config/bfin/bfin.c:3523 0xe3b0cb optimize_loop ../../gcc/gcc/hw-doloop.c:610 0xe3cb1e reorg_loops(bool, hw_doloop_hooks*) ../../gcc/gcc/hw-doloop.c:674 0xda055f bfin_reorg_loops ../../gcc/gcc/config/bfin/bfin.c:3908 0xda055f bfin_reorg ../../gcc/gcc/config/bfin/bfin.c:4650 0xa3a169 execute ../../gcc/gcc/reorg.c:4030 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. [root@localhost gcc]# /upstream/build-gcc-blackfin/gcc/xgcc -v Using built-in specs. COLLECT_GCC=/upstream/build-gcc-blackfin/gcc/xgcc Target: bfin-gchen-elf Configured with: ../gcc/configure --target=bfin-gchen-elf --disable-nls --disable-threads --disable-shared --disable-libssp --disable-libquadmath --disable-libgomp --disable-libatomic --prefix=/upstream/release-blackfin --without-headers --enable-languages=c,lto Thread model: single gcc version 6.0.0 20150620 (experimental) (GCC)
next reply other threads:[~2015-06-22 1:54 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-06-22 1:54 gang.chen.5i5j at gmail dot com [this message] 2015-06-22 7:55 ` [Bug target/66620] " miyuki at gcc dot gnu.org 2015-06-27 2:08 ` gang.chen.5i5j at gmail dot com 2015-06-27 2:17 ` gang.chen.5i5j at gmail dot com 2015-06-27 2:18 ` gang.chen.5i5j at gmail dot com 2015-06-27 2:20 ` gang.chen.5i5j at gmail dot com 2015-06-27 7:32 ` gang.chen.5i5j at gmail dot com 2015-06-28 9:45 ` gang.chen.5i5j at gmail dot com 2015-06-28 9:48 ` gang.chen.5i5j at gmail dot com 2015-06-28 13:54 ` gang.chen.5i5j at gmail dot com 2015-06-28 13:57 ` gang.chen.5i5j at gmail dot com 2015-06-28 13:58 ` gang.chen.5i5j at gmail dot com 2015-06-28 14:02 ` gang.chen.5i5j at gmail dot com 2015-09-03 2:45 ` gang.chen.5i5j at gmail 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-66620-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).