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: Sun, 28 Jun 2015 14:02:00 -0000	[thread overview]
Message-ID: <bug-66620-4-Wg1HOWRulM@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 #12 from Chen Gang <gang.chen.5i5j at gmail dot com> ---
Created attachment 35869
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=35869&action=edit
The result before lsetup optimization

The lsetup information is below:

lsetup (loop_begin, loop_end) count.

R0 will add 1 for each times, in our case, it is initialized to 0 before
lsetup().

After the loop_end, in our case, it needs "R0 += 1" to increase the last count.


  parent reply	other threads:[~2015-06-28 14:02 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
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 [this message]
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-Wg1HOWRulM@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).