public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/98338] [10/11 Regression] profiledbootstrap failure on x86_64-linux
Date: Sun, 14 Feb 2021 22:31:42 +0000	[thread overview]
Message-ID: <bug-98338-4-2pjpMKcPHO@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98338-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98338

--- Comment #17 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
I am testing
diff --git a/gcc/ipa-fnsummary.c b/gcc/ipa-fnsummary.c
index e32e69cd3ad..612880240dc 100644
--- a/gcc/ipa-fnsummary.c
+++ b/gcc/ipa-fnsummary.c
@@ -3137,11 +3137,18 @@ compute_fn_summary (struct cgraph_node *node, bool
early)
   info->estimated_stack_size = size_info->estimated_self_stack_size;

   /* Code above should compute exactly the same result as
-     ipa_update_overall_fn_summary but because computation happens in
-     different order the roundoff errors result in slight changes.  */
+     ipa_update_overall_fn_summary except for case when speculative
+     edges are present since these are accounted to size but not
+     self_size. Do not compare time since different order the roundoff
+     errors result in slight changes.  */
   ipa_update_overall_fn_summary (node);
-  /* In LTO mode we may have speculative edges set.  */
-  gcc_assert (in_lto_p || size_info->size == size_info->self_size);
+  if (flag_checking)
+    {
+      for (e = node->indirect_calls; e; e = e->next_callee)
+       if (e->speculative)
+         break;
+      gcc_assert (e || size_info->size == size_info->self_size);
+    }
 }

  parent reply	other threads:[~2021-02-14 22:31 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-17  0:50 [Bug bootstrap/98338] New: [11 " jakub at gcc dot gnu.org
2020-12-17  0:52 ` [Bug bootstrap/98338] " jakub at gcc dot gnu.org
2020-12-17  0:53 ` jakub at gcc dot gnu.org
2020-12-17  8:31 ` marxin at gcc dot gnu.org
2020-12-17  9:03 ` marxin at gcc dot gnu.org
2020-12-17  9:50 ` marxin at gcc dot gnu.org
2020-12-17  9:51 ` marxin at gcc dot gnu.org
2020-12-17 10:02 ` jakub at gcc dot gnu.org
2020-12-17 10:06 ` marxin at gcc dot gnu.org
2020-12-17 10:09 ` marxin at gcc dot gnu.org
2021-01-04 15:45 ` rguenth at gcc dot gnu.org
2021-01-28 16:08 ` jakub at gcc dot gnu.org
2021-01-28 21:26 ` hubicka at ucw dot cz
2021-01-28 21:34 ` hubicka at ucw dot cz
2021-01-29 17:16 ` jakub at gcc dot gnu.org
2021-02-01  8:26 ` marxin at gcc dot gnu.org
2021-02-12 17:32 ` marxin at gcc dot gnu.org
2021-02-12 17:33 ` [Bug bootstrap/98338] [10/11 " marxin at gcc dot gnu.org
2021-02-14 22:31 ` hubicka at gcc dot gnu.org [this message]
2021-02-26 12:21 ` jakub at gcc dot gnu.org
2021-02-26 17:07 ` hubicka at ucw dot cz
2021-02-26 17:36 ` jakub at gcc dot gnu.org
2021-02-26 17:38   ` Jan Hubicka
2021-02-26 17:38 ` hubicka at ucw dot cz
2021-02-26 17:42 ` jakub at gcc dot gnu.org
2021-03-01 12:25 ` jakub at gcc dot gnu.org
2021-03-01 13:37 ` cvs-commit at gcc dot gnu.org
2021-03-01 13:38 ` hubicka at gcc dot gnu.org
2021-03-02 14:54 ` cvs-commit 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-98338-4-2pjpMKcPHO@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).