From: Diego Novillo <dnovillo@redhat.com>
To: Alexandre Oliva <aoliva@redhat.com>
Cc: Carlo Wood <carlo@alinoe.com>, Michel LESPINASSE <walken@zoy.org>,
Andrew Haley <aph@redhat.com>,
gcc@gcc.gnu.org
Subject: Re: issues with inlining
Date: Sun, 19 Jan 2003 20:49:00 -0000 [thread overview]
Message-ID: <20030119153138.GA11146@tornado.toronto.redhat.com> (raw)
In-Reply-To: <orptqtfav3.fsf@free.redhat.lsd.ic.unicamp.br>
On Sun, 19 Jan 2003, Alexandre Oliva wrote:
> > Note that even with -O0 these blocks are removed... so why the
> > need to count those instruction when deciding whether or not to
> > inline the function?!
>
> Because we don't do many optimizations on trees yet. As we move
> optimization passes from RTL to trees, before function inlining, this
> should improve.
>
Right now, the tree optimizers are run after inlining has taken
place. This is convenient for us because we still can't do
IPA properly. Long term we should teach the tree optimizers
to work across procedures, but that is still a ways off.
Diego.
prev parent reply other threads:[~2003-01-19 15:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-18 18:32 Carlo Wood
2003-01-09 21:40 ` Michel LESPINASSE
2003-01-09 21:50 ` Andrew Haley
2003-01-09 22:52 ` Michel LESPINASSE
2003-01-10 0:15 ` Carlo Wood
2003-01-19 19:16 ` Alexandre Oliva
2003-01-19 20:49 ` Diego Novillo [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=20030119153138.GA11146@tornado.toronto.redhat.com \
--to=dnovillo@redhat.com \
--cc=aoliva@redhat.com \
--cc=aph@redhat.com \
--cc=carlo@alinoe.com \
--cc=gcc@gcc.gnu.org \
--cc=walken@zoy.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).