public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "xinliangli at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/35357] Loop peeling not happening
Date: Fri, 26 Oct 2012 16:56:00 -0000 [thread overview]
Message-ID: <bug-35357-4-IjEBIbhvbr@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-35357-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35357
--- Comment #2 from davidxl <xinliangli at gmail dot com> 2012-10-26 16:55:48 UTC ---
(In reply to comment #1)
> What is the expected optimization and what is its benefit?
Should be transformed into the following the simplified loop body.
void foo(int n)
{
int i;
if (n > 0) {
for ( i = 0; i < n; i++)
{
b[i*2] = a[3*i+1];
b[i*2] +=1;
}
b[i*2] = a[3*i + 1];
}
}
Icc at O2 distributes the loop body:
for ( i = 0; i <= n; i++)
{
b[i*2] = a[3*i+1];
}
for ( i = 0; i < n; i++)
{
b[i*2] += 1;
}
next parent reply other threads:[~2012-10-26 16:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-35357-4@http.gcc.gnu.org/bugzilla/>
2012-10-26 16:56 ` xinliangli at gmail dot com [this message]
2022-12-19 21:06 ` pinskia at gcc dot gnu.org
2008-02-25 5:02 [Bug middle-end/35357] New: " xinliangli at gmail dot com
2008-02-25 11:49 ` [Bug tree-optimization/35357] " rguenth at gcc dot gnu dot 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-35357-4-IjEBIbhvbr@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).