From: Richard Biener <rguenther@suse.de>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Jan Hubicka <hubicka@ucw.cz>, gcc-patches@gcc.gnu.org
Subject: Re: Non-dominating loop bounds in tree-ssa-loop-niter 3/4
Date: Wed, 31 Oct 2012 12:45:00 -0000 [thread overview]
Message-ID: <alpine.LNX.2.00.1210311334150.4063@zhemvz.fhfr.qr> (raw)
In-Reply-To: <20121031123408.GH1752@tucnak.redhat.com>
On Wed, 31 Oct 2012, Jakub Jelinek wrote:
> On Wed, Oct 31, 2012 at 01:30:02PM +0100, Richard Biener wrote:
> > On Wed, 31 Oct 2012, Jan Hubicka wrote:
> > > > unroll you mean. Because unrolling mutates the CFG too much.
> > > > Well - it was just a starting point, populating -Og with as little
> > > > as possible and 100% profitable transforms (in both debug and speed
> > > > metric). In late opts we only do (early opt queue is shared):
> > >
> > > Well, and what about early cunrolli?
> >
> > It's not there (and I would disable it for -Og).
>
> Generally, most of the loop transforms are undesirable for -Og.
Maybe with the exception of un-looping once rolling loops. But
yes, even loop header copying is undesirable in general.
Richard.
next prev parent reply other threads:[~2012-10-31 12:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-31 10:46 Jan Hubicka
2012-10-31 11:23 ` Richard Biener
2012-10-31 12:06 ` Jan Hubicka
2012-10-31 12:22 ` Richard Biener
2012-10-31 12:31 ` Jan Hubicka
2012-10-31 12:34 ` Richard Biener
2012-10-31 12:36 ` Jakub Jelinek
2012-10-31 12:45 ` Richard Biener [this message]
2012-10-31 14:18 ` Jan Hubicka
2012-10-31 14:07 ` Richard Biener
2012-12-01 19:22 ` H.J. Lu
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=alpine.LNX.2.00.1210311334150.4063@zhemvz.fhfr.qr \
--to=rguenther@suse.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=hubicka@ucw.cz \
--cc=jakub@redhat.com \
/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).