public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Diego Novillo <dnovillo@redhat.com>
To: Marty Hauff <marty.hauff@rmit.edu.au>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: [tree-ssa] Any good sources of documentation?
Date: Tue, 20 May 2003 12:19:00 -0000	[thread overview]
Message-ID: <1053430502.19956.91.camel@frodo.toronto.redhat.com> (raw)
In-Reply-To: <seca53da.044@its-mn-inet1.its.rmit.edu.au>

On Tue, 2003-05-20 at 02:12, Marty Hauff wrote:

>   From your response I am assuming that tree-ssa does not parse the
> _whole_ program into one huge tree but rather parses each function
> individually.
>
Mainline and tree-ssa are the same codebase (modulo the SSA bits).  You
could also use the call-graph in tree-ssa.  One thing we don't keep are
the SSA forms for each function separately.  That's a design limitation
that we would eventually need to overcome for whole program analysis.

>   I understand that this strategy uses far less memory but could
> tree-ssa be modified to parse the whole program into a single tree and
> if so would it break it?
> 
Sure.  It would need changing quite a few things, though.  You need to
support several flowgraphs at the same time, for instance.  Right now,
the flowgraph uses global data structures and variables.  There are some
efforts underway to build infrastructure to support whole program
analysis, so GCC will eventually grow enough brains to do this.

> Specifically I am trying to use the compiler to give me information
> about what hardware resources would be most useful for a given
> application.
>
Hardware resources?  I'm not sure I follow.  There is nothing
hardware-related in trees.


Diego.

       reply	other threads:[~2003-05-20 12:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <seca53da.044@its-mn-inet1.its.rmit.edu.au>
2003-05-20 12:19 ` Diego Novillo [this message]
2003-05-20 13:27 Marty Hauff
  -- strict thread matches above, loose matches on Subject: below --
2003-05-20  6:40 Marty Hauff
2003-05-19  8:49 Marty Hauff
2003-05-19 13:40 ` 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=1053430502.19956.91.camel@frodo.toronto.redhat.com \
    --to=dnovillo@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=marty.hauff@rmit.edu.au \
    /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).