public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andrew Pinski <pinskia@physics.uc.edu>
To: Mircea Namolaru <NAMOLARU@il.ibm.com>
Cc: "gcc@gcc.gnu.org list" <gcc@gcc.gnu.org>,
	Jan Hubicka <hubicka@ucw.cz>,
	apinski@apple.com, Andrew Pinski <pinskia@physics.uc.edu>
Subject: Re: Intermodule constant propagation
Date: Mon, 24 Nov 2003 10:10:00 -0000	[thread overview]
Message-ID: <21C0C1DD-1E58-11D8-B92B-000393A6D2F2@physics.uc.edu> (raw)
In-Reply-To: <OF16C5B090.092F529C-ON42256DE8.002C25F8-42256DE8.002D2FA9@il.ibm.com>

On Nov 24, 2003, at 00:13, Mircea Namolaru wrote:
> We would like to add several interprocedural optimizations to gcc, 
> starting
> with constant propagation.
>
> We are thinking of implementing a flow insensitive form of the
> interprocedural
> constant propagation algorithm described in [1][2], based on the new
> intermodule code 
> (http://gcc.gnu.org/ml/gcc-patches/2003-05/msg01665.html).
>
> We would appreciate any feedback regarding gcc interprocedural
> optimizations
> (work done or in development, potential problems etc).


Jan Hubicka and I were just talking about this on IRC today.

Here is the ideas both Jan and I agreed on (for the tree-ssa branch):
Have a flag called -fwhole-prgram which tells GCC that the whole
program is being compiled at this point and have variables which
were global be static.

Have the code in callgraph (aka cgraph.c) do some of the work:
Have cgraph_analyze_function to collect the assigments and uses
of variables.

And have any changes to the functions happen in cgraph_expand_fuction.

The down side at this point is that the trees here are in generic and 
not
gimple but Jan is working on getting this problem solved.

I might have some work done by the end of the week on this front and 
basic
constant propagation IPA.

Thanks,
Andrew Pinski
pinskia@physics.uc.edu
pinskia@gcc.gnu.org
apinski@apple.com

  reply	other threads:[~2003-11-24  8:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-24  9:41 Mircea Namolaru
2003-11-24 10:10 ` Andrew Pinski [this message]
2003-11-24 19:43   ` Jan Hubicka
2003-11-24 20:24     ` Dan Nicolaescu
2003-11-24 20:46       ` Andrew Pinski
2003-11-24 22:39         ` Geoff Keating
2003-11-25  0:44           ` Andrew Pinski
2003-11-25  9:41             ` Andrew Pinski
2003-11-25 13:27             ` Jan Hubicka
2003-11-25 23:04             ` Geoff Keating
2003-11-26  6:03               ` Andrew Pinski
2003-11-26 21:06                 ` Geoff Keating
2003-12-08 15:23 Mircea Namolaru
2003-12-08 16:31 ` 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=21C0C1DD-1E58-11D8-B92B-000393A6D2F2@physics.uc.edu \
    --to=pinskia@physics.uc.edu \
    --cc=NAMOLARU@il.ibm.com \
    --cc=apinski@apple.com \
    --cc=gcc@gcc.gnu.org \
    --cc=hubicka@ucw.cz \
    /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).