public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/42971]  New: GCC cannot perform partial inlining
Date: Fri, 05 Feb 2010 11:08:00 -0000	[thread overview]
Message-ID: <bug-42971-10053@http.gcc.gnu.org/bugzilla/> (raw)

Inlining of guards is important for optimizing.  Consider

int flag;

int foo (void)
{
  if (!flag)
    return 0;

  ...
}

we should be able to partially inline foo into its callers transforming


  if (foo ())
    {
       ...
    }
  else
    {
       ...
    }

to

   if (!flag)
     <ret> = 0;
   else
     <ret> = foo.clone();
   if (<ret>)
     {
        ...
     }
   else
     {
        ...
     }

to be able to perform optimizations across the path where foo.clone
is not executed.


-- 
           Summary: GCC cannot perform partial inlining
           Product: gcc
           Version: 4.5.0
            Status: UNCONFIRMED
          Keywords: missed-optimization
          Severity: enhancement
          Priority: P3
         Component: tree-optimization
        AssignedTo: hubicka at gcc dot gnu dot org
        ReportedBy: rguenth at gcc dot gnu dot org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42971


             reply	other threads:[~2010-02-05 11:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-05 11:08 rguenth at gcc dot gnu dot org [this message]
2010-02-07 21:01 ` [Bug tree-optimization/42971] " pinskia at gcc dot gnu dot org
2010-07-31 22:15 ` hubicka at gcc dot gnu dot org

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=bug-42971-10053@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).