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] bfin: bfin.c: (hwloop_optimize): gcc_assert (JUMP_P (insn)) fails.
Date: Sat, 27 Jun 2015 02:08:00 -0000 [thread overview]
Message-ID: <bug-66620-4-f675PHPQJ1@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-66620-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66620
--- Comment #2 from Chen Gang <gang.chen.5i5j at gmail dot com> ---
(In reply to Mikhail Maltsev from comment #1)
> Started with r208165.
OK, thanks. Really it is, it is valuable to me (it can generate the correct
insns for comparing). And also if remove "-fno-reorder-blocks", it can generate
correct insns too (after comparing with the original correct insns, this
optimized insns are correct).
In our case, the issue insn is:
(insn 132 59 74 6 (parallel [
(set (reg:SI 45 LT1)
(label_ref 74))
(set (reg:SI 49 LB1)
(label_ref 133))
(set (reg:SI 47 LC1)
(reg:SI 8 P0 [112]))
]) lpt_commit.i:11 -1
(nil))
it is in an incorrect area, which want to optimize the insns below in another
area:
(note 68 67 69 9 [bb 9] NOTE_INSN_BASIC_BLOCK)
(insn:TI 69 68 109 9 (set (reg/v:SI 0 R0 [orig:94 iip ] [94])
(plus:SI (reg/v:SI 0 R0 [orig:94 iip ] [94])
(const_int 1 [0x1]))) lpt_commit.i:19 50 {addsi3}
(nil))
(jump_insn:TI 109 69 73 9 (parallel [
(set (pc)
(if_then_else (ne (reg:SI 8 P0 [112])
(const_int 1 [0x1]))
(label_ref:SI 70)
(pc)))
(set (reg:SI 8 P0 [112])
(plus:SI (reg:SI 8 P0 [112])
(const_int -1 [0xffffffffffffffff])))
(unspec [
(const_int 0 [0])
] 10)
(clobber (scratch:SI))
]) lpt_commit.i:19 96 {loop_end}
(int_list:REG_BR_PROB 7384 (nil))
-> 70)
The incorrect insn wants to merge the too "for (iip = 0; iip < 4; iip++) {...}"
in one.
Next, I shall continue analyzing it, and the all related insns are in
attachments. And welcome any ideas, suggestions and completions, Thanks.
next prev parent reply other threads:[~2015-06-27 2:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-22 1:54 [Bug target/66620] New: " gang.chen.5i5j at gmail dot com
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 [this message]
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-f675PHPQJ1@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: link
Be 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).