public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rakdver at atrey dot karlin dot mff dot cuni dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/31040] unroll/peel loops not aggressive enough
Date: Mon, 05 Mar 2007 11:50:00 -0000 [thread overview]
Message-ID: <20070305114957.7670.qmail@sourceware.org> (raw)
In-Reply-To: <bug-31040-6642@http.gcc.gnu.org/bugzilla/>
------- Comment #3 from rakdver at atrey dot karlin dot mff dot cuni dot cz 2007-03-05 11:49 -------
Subject: Re: unroll/peel loops not aggressive enough
> We don't unroll non-innermost loops at the moment. I don't know if sccp can
> be taught to handle this case (and if it's worth it).
It is fairly easy to make gcc completely unroll non-innermost loops, I
am working on that.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31040
next prev parent reply other threads:[~2007-03-05 11:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-05 9:11 [Bug tree-optimization/31040] New: " jv244 at cam dot ac dot uk
2007-03-05 10:18 ` [Bug tree-optimization/31040] " rguenth at gcc dot gnu dot org
2007-03-05 11:47 ` jv244 at cam dot ac dot uk
2007-03-05 11:50 ` rakdver at atrey dot karlin dot mff dot cuni dot cz [this message]
2007-03-05 12:22 ` rguenth at gcc dot gnu dot org
2007-07-03 18:21 ` jv244 at cam dot ac dot uk
2007-07-21 8:59 ` pinskia 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=20070305114957.7670.qmail@sourceware.org \
--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).