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 ipa/60315] [4.8/4.9 Regression] template constructor switch optimization
Date: Mon, 24 Feb 2014 13:00:00 -0000	[thread overview]
Message-ID: <bug-60315-4-hWwIYmyHZs@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60315-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
When calling do_estimate_edge_size to compute the effect on caller size when
inlining an edge we call estimate_node_size_and_time which eventually recurses
down to estimate_calls_size_and_time (why!?  call edges in the callee are
irrelevant when inlining the call into the caller!).  Doesn't this just want
to add(?) e->call_stmt_size/time?  At the moment estimate_calls_size_and_time
recurses to estimate_edge_size_and_time ... and I don't see _any_ prevention
of running in cgraph cycles here.  (and the cache isn't populated before
computing an edges size/time is).

In fact,

Index: gcc/ipa-inline-analysis.c
===================================================================
--- gcc/ipa-inline-analysis.c   (revision 207960)
+++ gcc/ipa-inline-analysis.c   (working copy)
@@ -3011,21 +3011,11 @@ estimate_calls_size_and_time (struct cgr
       struct inline_edge_summary *es = inline_edge_summary (e);
       if (!es->predicate
          || evaluate_predicate (es->predicate, possible_truths))
-       {
-         if (e->inline_failed)
-           {
-             /* Predicates of calls shall not use NOT_CHANGED codes,
-                sowe do not need to compute probabilities.  */
-             estimate_edge_size_and_time (e, size, time, REG_BR_PROB_BASE,
-                                          known_vals, known_binfos,
-                                          known_aggs, hints);
-           }
-         else
-           estimate_calls_size_and_time (e->callee, size, time, hints,
-                                         possible_truths,
-                                         known_vals, known_binfos,
-                                         known_aggs);
-       }
+       /* Predicates of calls shall not use NOT_CHANGED codes,
+          sowe do not need to compute probabilities.  */
+       estimate_edge_size_and_time (e, size, time, REG_BR_PROB_BASE,
+                                    known_vals, known_binfos,
+                                    known_aggs, hints);
     }
   for (e = node->indirect_calls; e; e = e->next_callee)
     {

fixes this and I cannot make sense of calling estimate_calls_size_and_time
for the callee of an edge that we are not going to inline (or that is already
inlined?  I still find those if (e->inline_failed) checks odd).  If it's
supposed to account for inline bodies in the caller then we should have
updated the inline_summary () of the caller, not have to recurse here - and
we _do_ seem to (inline_merge_summary).


  parent reply	other threads:[~2014-02-24 13:00 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-22  5:53 [Bug c++/60315] New: " garcia.espinosa.jr at gmail dot com
2014-02-22  9:00 ` [Bug ipa/60315] [4.8/4.9 Regression] " glisse at gcc dot gnu.org
2014-02-22 13:59 ` rguenth at gcc dot gnu.org
2014-02-24 11:27 ` rguenth at gcc dot gnu.org
2014-02-24 11:36 ` rguenth at gcc dot gnu.org
2014-02-24 13:00 ` rguenth at gcc dot gnu.org [this message]
2014-02-24 13:48 ` rguenth at gcc dot gnu.org
2014-02-24 13:50 ` rguenth at gcc dot gnu.org
2014-02-24 14:22 ` rguenth at gcc dot gnu.org
2014-02-27  9:35 ` rguenth at gcc dot gnu.org
2014-03-18 11:44 ` jakub at gcc dot gnu.org
2014-03-24 22:44 ` hubicka at gcc dot gnu.org
2014-03-24 23:01 ` hubicka at gcc dot gnu.org
2014-03-24 23:35 ` hubicka at gcc dot gnu.org
2014-03-25  5:44 ` hubicka at gcc dot gnu.org
2014-03-26  2:12 ` hubicka at gcc dot gnu.org
2014-03-26  2:20 ` hubicka at gcc dot gnu.org
2014-03-26  9:00 ` rguenther at suse dot de
2014-03-26 21:58 ` hubicka at ucw dot cz
2014-03-27  7:30 ` rguenther at suse dot de
2014-05-22  9:06 ` [Bug ipa/60315] [4.8/4.9/4.10 " rguenth at gcc dot gnu.org
2014-12-19 13:28 ` [Bug ipa/60315] [4.8/4.9/5 " jakub at gcc dot gnu.org
2015-02-24 11:00 ` jakub at gcc dot gnu.org
2015-02-24 11:42 ` [Bug ipa/60315] [4.8 " rguenth at gcc dot gnu.org
2015-06-23  8:48 ` 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-60315-4-hWwIYmyHZs@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).