From: Marcio de Oliveira Buss <ra990898@ic.unicamp.br>
To: gcc@gcc.gnu.org
Subject: CFG
Date: Wed, 28 Jun 2000 13:47:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.10.10006281746080.16817-100000@xingu.dcc.unicamp.br> (raw)
Good Morning (afternoon) to all...
Could you please help me? I want to know if the CFG constructed
in the dataflow analysis is updated at each step subsequent steps of
the compilation, and, in turn, remains until the Final phase of the
compilation process. I want to transform the CFG into another structure
but only after all the optimizations have been made over it. I know
that the almost all optimizations are made over the RTL expressions,
but I don't know if some optimization touchs the CFG.
In other words, I would like to know if the CFG is destructed
after the dataflow analysis, i.e., after the informations provided
by the CFG are recorded for futures uses, or if the CFG remains
untouchable.
Thanks.
Best Regards,
Marcio.
next reply other threads:[~2000-06-28 13:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-28 13:47 Marcio de Oliveira Buss [this message]
2000-06-28 14:15 ` CFG Jeffrey A Law
2000-06-28 14:36 ` CFG Marcio de Oliveira Buss
2000-06-28 17:06 ` CFG Richard Henderson
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.10.10006281746080.16817-100000@xingu.dcc.unicamp.br \
--to=ra990898@ic.unicamp.br \
--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).