public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Ollie Wild" <aaw@google.com>
To: "Praveen Raghavan" <praveen.gcc@gmail.com>
Cc: "Diego Novillo" <dnovillo@google.com>, gcc@gcc.gnu.org
Subject: Re: [RFC] WHOPR - A whole program optimizer framework for GCC
Date: Thu, 13 Dec 2007 08:10:00 -0000	[thread overview]
Message-ID: <65dd6fd50712122353g693ae907ob43221ac3ac2f6e4@mail.gmail.com> (raw)
In-Reply-To: <738f85410712122314y75cfe3acyb3a7b1d6ef99044@mail.gmail.com>

On Dec 12, 2007 11:14 PM, Praveen Raghavan <praveen.gcc@gmail.com> wrote:
>
> 1. Are there also plans to extend the global transformation
> capabilities. I see that the original set of global transformations is
> limited (rightfully so).

This is still at a very early design stage.  Additional
transformations could (and should) be added where they make sense.
The main constraints to consider are the time and memory requirements
of the WPA phase.  Since this is the only phase which can't be
parallelized, its scalability is paramount.

> 2. Also any thoughts on how you keep the complete GIMPLE
> representation of millions of functions together? You would have some
> serious complexity issues inside the WPA engine?
> Or is it the idea that you start with the minimal information in the
> wpo1 file and if required read in the GIMPLE section?

You don't.  WPA is the only global phase, and it operates only on
summary data.  The actually reading of GIMPLE occurs in LTRANS, which
partitions the problem.  Depending on how large partitions need to be
before reasonable performance benefits are observed, it may be
necessary to allow LTRANS to swap functions in and out of memory.
That's still an open question.

> 3. Is there a plan/schedule on when 'a' version of this would be out?

TBD.

Ollie

  reply	other threads:[~2007-12-13  7:53 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-12 20:54 Diego Novillo
2007-12-12 23:32 ` Tim Josling
2007-12-13  7:53   ` Ollie Wild
2007-12-13 14:09     ` Diego Novillo
2007-12-19 22:29       ` Tim Josling
2007-12-19 22:29         ` Diego Novillo
2007-12-19 22:34         ` Chris Lattner
2007-12-19 22:49           ` Diego Novillo
2007-12-13  0:03 ` Harvey Harrison
2007-12-13  0:11   ` Chris Lattner
2007-12-13  7:14     ` Harvey Harrison
2007-12-13 14:41   ` Diego Novillo
2007-12-13 19:06     ` Chris Lattner
2007-12-13  7:32 ` Praveen Raghavan
2007-12-13  8:10   ` Ollie Wild [this message]
2007-12-18 13:48 ` Jan Hubicka
2007-12-19 17:22   ` Diego Novillo
2007-12-19 18:55     ` Kenneth Zadeck
2007-12-20  3:48       ` Diego Novillo
2007-12-20  4:59         ` Kenneth Zadeck
2007-12-20  8:53     ` Jan Hubicka
2007-12-12 21:15 J.C. Pizarro
2007-12-12 22:42 ` Jonathan Wakely
2007-12-12 22:42   ` J.C. Pizarro
2007-12-12 22:50     ` Daniel Jacobowitz
2007-12-12 23:29     ` Sebastian Pop
2007-12-13 10:22     ` Paolo Bonzini
2007-12-13 13:32     ` Nicholas Nethercote

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=65dd6fd50712122353g693ae907ob43221ac3ac2f6e4@mail.gmail.com \
    --to=aaw@google.com \
    --cc=dnovillo@google.com \
    --cc=gcc@gcc.gnu.org \
    --cc=praveen.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).