public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: James Michael DuPont <mdupont777@yahoo.com>
To: Diego Novillo <dnovillo@acm.org>,
	Bryce McKinlay <bryce@waitaki.otago.ac.nz>
Cc: James Michael DuPont <mdupont777@yahoo.com>,
	Joe Buck <Joe.Buck@synopsys.com>,
	gcc@gnu.org
Subject: Re: Linkage of GPLed GCC to Closed Source via XML or Perl
Date: Sun, 03 Mar 2002 22:52:00 -0000	[thread overview]
Message-ID: <20020304065253.56575.qmail@web13308.mail.yahoo.com> (raw)
In-Reply-To: <20020304025838.GA30279@tornado.toronto.redhat.com>

> If you're looking for more interesting ways of
> examining the
> ASTs, the ast-optimizer-branch is starting to show a
> few:
> 
> - Unparsing capabilities (could potentially be used
> as a
>   source-to-source converter).
> 
> - Flowgraphs.
> 
> - Call graphs.
> 
> - Metrics (control flow complexity and logical
> complexity).

That sounds really exciting!
I have to admit that I have not looked at that branch
yet. 
The next step would of course to start putting  the
flow and call graphs into a file so that you can
examine the program on a whole.

I will start looking into the ast optimiser this week.

mike

=====
James Michael DuPont

__________________________________________________
Do You Yahoo!?
Yahoo! Sports - sign up for Fantasy Baseball
http://sports.yahoo.com

  reply	other threads:[~2002-03-04  6:52 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-28  4:04 James Michael DuPont
2002-02-28  8:07 ` Joe Buck
2002-03-01  8:01   ` James Michael DuPont
2002-03-01  8:55     ` Joe Buck
2002-03-02  1:21       ` James Michael DuPont
2002-03-03 18:35         ` Bryce McKinlay
2002-03-03 18:58           ` Diego Novillo
2002-03-03 22:52             ` James Michael DuPont [this message]
2002-03-03 22:52           ` James Michael DuPont
2002-03-03 19:39         ` Alexandre Oliva
2002-03-03 23:46           ` James Michael DuPont
2002-02-28  8:54 James Michael DuPont
2002-02-28 10:27 ` Joe Buck
2002-02-28 11:22 Bernard Dautrevaux
2002-02-28 12:17 ` Joe Buck
2002-02-28 11:46 mike stump
2002-02-28 12:40 James Michael DuPont
2002-02-28 20:32 Robert Dewar
2002-02-28 20:44 Robert Dewar
2002-02-28 21:56 Robert Dewar
2002-02-28 22:51 ` Daniel Berlin
2002-03-01  9:34 Bernard Dautrevaux
2002-03-02  1:26 ` James Michael DuPont
2002-03-03 19:06 Robert Dewar
2002-03-03 19:14 ` Diego Novillo
2002-03-03 23:27 ` James Michael DuPont
2002-03-04  5:40   ` Diego Novillo
2002-03-04  1:52 Robert Dewar
2002-03-04  1:56 ` James Michael DuPont
2002-03-07 13:10 ` Florian Weimer
2002-03-07 14:32 Robert Dewar

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=20020304065253.56575.qmail@web13308.mail.yahoo.com \
    --to=mdupont777@yahoo.com \
    --cc=Joe.Buck@synopsys.com \
    --cc=bryce@waitaki.otago.ac.nz \
    --cc=dnovillo@acm.org \
    --cc=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).