From: Andrew MacLeod <amacleod@redhat.com>
To: Diego Novillo <dnovillo@redhat.com>
Cc: Richard Guenther <rguenth@tat.physik.uni-tuebingen.de>,
gcc mailing list <gcc@gcc.gnu.org>
Subject: Re: tree-ssa branch: Call for preliminary testing
Date: Fri, 13 Jun 2003 20:15:00 -0000 [thread overview]
Message-ID: <1055528231.19440.1453.camel@p4> (raw)
In-Reply-To: <1055433764.824.297.camel@frodo.toronto.redhat.com>
On Thu, 2003-06-12 at 12:02, Diego Novillo wrote:
> On Mon, 2003-05-12 at 09:01, Richard Guenther wrote:
>
> > Got it compile on a 2Gig machine - .ii file can be fetched from
> >
> > http://www.tat.physik.uni-tuebingen.de/~rguenth/FieldCentering.cmpl.ii.gz
> >
> > the test uses max. 1.5GB ram on this machine.
> >
> > Richard.
> >
> Seems partially fixed now. It takes 19 minutes to compile, though. But!
> it doesn't use more than 300Mb of core now.
>
> $ /usr/bin/time gcc/cc1plus -ftemplate-depth-80 -fno-exceptions -Drestrict=__restrict__ -DNOPAssert -DNOCTAssert -O2 -march=athlon -funroll-loops -fomit-frame-pointer --param min-inline-insns=200 -quiet FieldCentering.cmpl.ii 1106.46user 1.19system
> 18:55.17elapsed 97%CPU (0avgtext+0avgdata 0maxresident)k 0inputs+0outputs (1205major+142535minor)pagefaults 0swaps
>
> In contrast, this uses 200Mb of core in mainline and takes 17 seconds to
> compile. I'm thinking this and Gerald's PR8361 are good test cases :)
>
> $ /usr/bin/time ~/merge-tree-ssa/mainline/native/bld.tobiano/gcc/cc1plus -ftemplate-depth-80 -fno-exceptions -Drestrict=__restrict__ -DNOPAssert -DNOCTAssert -O2 -march=athlon -funroll-loops -fomit-frame-pointer --param min-inline-insns=200 -quiet FieldCentering.cmpl.ii
> 16.29user 0.75system 0:17.13elapsed 99%CPU (0avgtext+0avgdata 0maxresident)k
> 0inputs+0outputs (1134major+109771minor)pagefaults 0swaps
>
OK, I just posted a patch to speed up DCE, which was the culprit here.
On my machine, DCE went from using 1678 seconds to 3.5 seconds.
This'll probably help all of POOMA, and most C++ programs.
Andrew
(PS, the patch is checked in. tree-ssa-dce.c)
next prev parent reply other threads:[~2003-06-13 18:17 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-11 17:11 Richard Guenther
2003-05-12 12:43 ` Diego Novillo
2003-05-12 12:58 ` Steven Bosscher
2003-05-12 13:08 ` Andrew MacLeod
2003-05-12 13:16 ` Diego Novillo
2003-05-12 13:22 ` Andrew MacLeod
2003-05-12 13:49 ` Richard Guenther
2003-05-12 14:05 ` Daniel Berlin
2003-05-12 14:16 ` Andrew MacLeod
2003-05-12 14:17 ` Diego Novillo
2003-06-12 15:36 ` Diego Novillo
2003-05-12 13:02 ` Steven Bosscher
2003-05-12 13:09 ` Diego Novillo
2003-05-12 13:59 ` Daniel Berlin
2003-05-12 14:12 ` Andrew MacLeod
2003-05-12 13:02 ` Richard Guenther
2003-06-12 16:09 ` Diego Novillo
2003-06-12 21:10 ` Richard Guenther
2003-06-12 21:29 ` Diego Novillo
2003-06-13 9:58 ` Richard Guenther
2003-06-13 11:38 ` Diego Novillo
2003-06-14 11:41 ` Richard Guenther
2003-06-13 20:15 ` Andrew MacLeod [this message]
2003-06-14 20:06 ` Richard Guenther
-- strict thread matches above, loose matches on Subject: below --
2003-05-12 2:13 John David Anglin
2003-05-12 12:43 ` Diego Novillo
2003-05-15 17:50 ` John David Anglin
2003-05-15 19:32 ` Diego Novillo
2003-05-07 14:25 Diego Novillo
2003-05-07 14:30 ` Diego Novillo
2003-05-07 17:54 ` Qiong Cai
2003-05-07 18:02 ` law
2003-05-09 1:31 ` Qiong Cai
2003-05-09 2:02 ` Andrew Pinski
2003-05-07 18:24 ` Daniel Berlin
2003-05-08 5:51 ` Toon Moene
2003-05-08 13:26 ` Diego Novillo
2003-05-09 16:46 ` Gerald Pfeifer
2003-05-09 17:28 ` Diego Novillo
2003-05-09 17:37 ` Diego Novillo
2003-05-09 19:02 ` Eric Botcazou
2003-05-10 14:19 ` Gerald Pfeifer
2003-05-10 14:43 ` Graham Stott
2003-05-10 15:34 ` Daniel Berlin
2003-05-12 12:43 ` Diego Novillo
2003-05-10 15:04 ` Gerald Pfeifer
2003-05-12 14:21 ` Gerald Pfeifer
2003-05-12 16:27 ` Steven Bosscher
2003-05-20 10:44 ` Gerald Pfeifer
2003-05-20 11:39 ` Diego Novillo
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=1055528231.19440.1453.camel@p4 \
--to=amacleod@redhat.com \
--cc=dnovillo@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=rguenth@tat.physik.uni-tuebingen.de \
/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).