public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Kyung-suk Lhee <klhee@ecs.syr.edu>
To: Devang Patel <dpatel@apple.com>
Cc: gcc@gcc.gnu.org
Subject: Re: saving tree structure
Date: Thu, 22 Aug 2002 10:18:00 -0000	[thread overview]
Message-ID: <Pine.GSO.4.44.0208221257330.5606-100000@apollo.ecs.syr.edu> (raw)
In-Reply-To: <1DAC5A6D-B56D-11D6-A533-00039310EDEA@>

I downloaded the gcc3 and now reading
the src files. it may be exactly what I was looking
for ... I was considering SUIF too, which could be
easier for my case, but modifying gcc is so tempting
(even though I'm not that good programmer) since gcc
is so dependable and would let me easily compile many
programs.
thanks,
kyung-suk

On Wed, 21 Aug 2002, Devang Patel wrote:

>
> On Wednesday, August 21, 2002, at 01:52  PM, Kyung-suk Lhee wrote:
>
> > hi,
> > I'm trying to save the tree (AST) to a file so
> > that I can compile it later. I need to do this
> > to perform interprocedural analysis before producing
> > an executable. I'm wondering if this would be
> > doable, or if anybody did a similar work on gcc.
>
> PFE saves trees and lot more on the disk and restores
> it during next compilation. Search for Stan Sheb's PFE related
> mail in this mailing list archive to find out how to get it.
>
> (PFE is Apple's precompiled header implementation in gcc3)
>
> -Devang
>

      reply	other threads:[~2002-08-22 10:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-21 13:52 Kyung-suk Lhee
2002-08-21 18:19 ` Devang Patel
2002-08-22 10:18   ` Kyung-suk Lhee [this message]

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=Pine.GSO.4.44.0208221257330.5606-100000@apollo.ecs.syr.edu \
    --to=klhee@ecs.syr.edu \
    --cc=dpatel@apple.com \
    --cc=gcc@gcc.gnu.org \
    /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).