public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Jason Merrill <jason@redhat.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: optimization/9767 - question on inlining functions vs. member functions
Date: Fri, 28 Feb 2003 20:26:00 -0000	[thread overview]
Message-ID: <20030228202602.22433.qmail@sources.redhat.com> (raw)

The following reply was made to PR optimization/9767; it has been noted by GNATS.

From: Jason Merrill <jason@redhat.com>
To: Benjamin Kosnik <bkoz@redhat.com>
Cc: rth@redhat.com, gcc-gnats@gcc.gnu.org
Subject: Re: optimization/9767 - question on inlining functions vs. member
 functions
Date: Fri, 28 Feb 2003 15:20:54 -0500

 OK, the problem is with the design of the inliner.  In many cases, whether
 or not a function gets inlined depends on whether or not it has already
 been expanded--and as a result, had inline expansion done on it.  _M_write
 has 14 statements before optimize_inline_calls, and 49 after, which makes
 it no longer a candidate for inlining.  In your explicit instantiation
 testcase, instantiating the whole class instantiates _M_write before write,
 so _M_write can't be inlined; if you just instantiate write, _M_write has
 not been expanded, so it can still be inlined.
 
 One fix would be to keep a copy of the original function trees for use in
 inlining.  Optimal inlining strategy is still a topic of debate...
 
 Jason


                 reply	other threads:[~2003-02-28 20:26 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20030228202602.22433.qmail@sources.redhat.com \
    --to=jason@redhat.com \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).