From: Richard Biener <rguenther@suse.de>
To: Steven Bosscher <stevenb.gcc@gmail.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH][6/n] tree LIM TLC
Date: Tue, 12 Mar 2013 15:33:00 -0000 [thread overview]
Message-ID: <alpine.LNX.2.00.1303121630390.3543@zhemvz.fhfr.qr> (raw)
In-Reply-To: <CABu31nN+nC_aUwEbEY9ambq9Facg_X1=W8jC62E38-TNqLfnmw@mail.gmail.com>
On Tue, 12 Mar 2013, Steven Bosscher wrote:
> On Tue, Mar 12, 2013 at 4:25 PM, Richard Biener wrote:
> >
> > (Un-?)surprisingly the most effective compile-time reduction for
> > the testcase in PR39326 is to employ ao_ref caching for
> > alias oracle queries and caching of expanded affine-combinations
> > for affine disambiguations.
> >
> > This reduces compile-time to a manageable amount in the first place
> > for me (so I'm sending it "late" in the series).
>
> I suppose this renders my LIM patch obsolete.
Not really - it's still
tree loop invariant motion: 588.31 (78%) usr
so limiting the O(n^2) dependence testing is a good thing. But I
can take it over from here and implement that ontop of my patches
if you like.
> Did you also look at the memory foot print?
Yeah, unfortunately processing outermost loops separately doesn't
reduce peak memory consumption. I'll look into getting rid of the
all-refs bitmaps, but I'm not there yet.
Currently the testcase peaks at 1.7GB for me (after LIM, then
it gets worse with DSE and IRA). And I only tested -O1 sofar.
Thanks,
Richard.
next prev parent reply other threads:[~2013-03-12 15:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-12 15:25 Richard Biener
2013-03-12 15:29 ` Steven Bosscher
2013-03-12 15:33 ` Richard Biener [this message]
2013-03-12 16:01 ` Steven Bosscher
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.1303121630390.3543@zhemvz.fhfr.qr \
--to=rguenther@suse.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=stevenb.gcc@gmail.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).