From: Richard Henderson <rth@cygnus.com>
To: Marcio de Oliveira Buss <ra990898@ic.unicamp.br>
Cc: gcc@gcc.gnu.org
Subject: Re: CFG
Date: Wed, 28 Jun 2000 17:06:00 -0000 [thread overview]
Message-ID: <20000628170608.B17113@cygnus.com> (raw)
In-Reply-To: <Pine.GSO.4.10.10006281828210.19391-100000@xingu.dcc.unicamp.br>
On Wed, Jun 28, 2000 at 06:35:50PM -0300, Marcio de Oliveira Buss wrote:
> Thus, is there an answer for this question?
> "what is the compilation point where I could take the most
> optimized CFG for a function to build another structure based on that
> CFG?" And which is the file representing this point.
You can rebuild the CFG at almost any point before delayed-branch
scheduling. I.e. before dbr_schedule. Of course, what you have in
mind fror "build another structure" may also influence where things
may occur.
r~
prev parent reply other threads:[~2000-06-28 17:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-28 13:47 CFG Marcio de Oliveira Buss
2000-06-28 14:15 ` CFG Jeffrey A Law
2000-06-28 14:36 ` CFG Marcio de Oliveira Buss
2000-06-28 17:06 ` Richard Henderson [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=20000628170608.B17113@cygnus.com \
--to=rth@cygnus.com \
--cc=gcc@gcc.gnu.org \
--cc=ra990898@ic.unicamp.br \
/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).