public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/47663] Very simple wrapper not inlined
Date: Wed, 06 Apr 2011 08:51:00 -0000	[thread overview]
Message-ID: <bug-47663-4-qAQpH11n3E@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47663-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from Richard Guenther <rguenth at gcc dot gnu.org> 2011-04-06 08:51:27 UTC ---
Author: rguenth
Date: Wed Apr  6 08:51:23 2011
New Revision: 172023

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=172023
Log:
2011-04-06  Richard Guenther  <rguenther@suse.de>

    PR tree-optimization/47663
    * cgraph.h (struct cgraph_edge): Add call_stmt_size and
    call_stmt_time fields.
    (cgraph_edge_inlinable_p): Declare.
    (cgraph_edge_recursive_p): New inline function.
    * cgraph.c (cgraph_create_edge_1): Initialize call_stmt_size.
    (cgraph_clone_edge): Copy it.
    * ipa-inline.c (cgraph_estimate_edge_time): New function.
    Account for call stmt time.
    (cgraph_estimate_time_after_inlining): Take edge argument.
    (cgraph_estimate_edge_growth): Account call stmt size.
    (cgraph_estimate_size_after_inlining): Take edge argument.
    (cgraph_mark_inline_edge): Adjust.
    (cgraph_check_inline_limits): Likewise.
    (cgraph_recursive_inlining_p): Remove.
    (cgraph_edge_badness): Use cgraph_edge_recursive_p.
    (cgraph_decide_recursive_inlining): Take edge argument and
    adjust.
    (cgraph_decide_inlining_of_small_functions): Do not avoid
    diags for recursive inlining here.
    (cgraph_flatten): Adjust.
    (cgraph_decide_inlining_incrementally): Likewise.
    (estimate_function_body_sizes): Remove call cost handling.
    (compute_inline_parameters): Initialize caller edge call costs.
    (cgraph_estimate_edge_growth): New function.
    (cgraph_estimate_growth): Use it.
    (cgraph_edge_badness): Likewise.
    (cgraph_check_inline_limits): Take an edge argument.
    (cgraph_decide_inlining_of_small_functions): Adjust.
    (cgraph_decide_inlining): Likewise.
    * tree-inline.c (estimate_num_insns): Only account for call
    return value if it is used.
    (expand_call_inline): Avoid diagnostics on recursive inline
    functions here.
    * lto-cgraph.c (lto_output_edge): Output edge call costs.
    (input_edge): Input edge call costs.

    * gcc.dg/tree-ssa/inline-8.c: New testcase.

Added:
    trunk/gcc/testsuite/gcc.dg/tree-ssa/inline-8.c
Modified:
    trunk/gcc/ChangeLog
    trunk/gcc/cgraph.c
    trunk/gcc/cgraph.h
    trunk/gcc/ipa-inline.c
    trunk/gcc/lto-cgraph.c
    trunk/gcc/testsuite/ChangeLog
    trunk/gcc/tree-inline.c


  parent reply	other threads:[~2011-04-06  8:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-09 15:52 [Bug middle-end/47663] New: " rguenth at gcc dot gnu.org
2011-02-09 16:20 ` [Bug middle-end/47663] " rguenth at gcc dot gnu.org
2011-02-10 13:08 ` rguenth at gcc dot gnu.org
2011-02-22 14:28 ` rguenth at gcc dot gnu.org
2011-04-06  8:51 ` rguenth at gcc dot gnu.org [this message]
2011-04-06 10:11 ` rguenth at gcc dot gnu.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-47663-4-qAQpH11n3E@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).