public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hubicka at ucw dot cz" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug analyzer/98599] [11 Regression] fatal error: Cgraph edge statement index out of range with -Os -flto -fanalyzer Date: Tue, 13 Apr 2021 07:55:24 +0000 [thread overview] Message-ID: <bug-98599-4-1xuiHQWcar@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98599-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98599 --- Comment #15 from Jan Hubicka <hubicka at ucw dot cz> --- > Should be fixed by the above patch, though it's more of a workaround for now; > am still not sure about what's going on with clones. I undestand it now. The problem is that fixup is missed for one gimple body after statements was renumbered by analyzer. The reason is confused check for has_gimple_body_p. We do not really get out of sync between uids of functions and its clone, since we stream only clone, but with the fact that stream in code expects uids to be continuously increasing. So apparenlty analyzer is first pass that does use UIDs of statements at WPA time. Sorry for taking so long time to understand this. diff --git a/gcc/lto/lto.c b/gcc/lto/lto.c index ceb61bb300b..5903f75ac23 100644 --- a/gcc/lto/lto.c +++ b/gcc/lto/lto.c @@ -306,7 +306,7 @@ lto_wpa_write_files (void) cgraph_node *node; /* Do body modifications needed for streaming before we fork out worker processes. */ - FOR_EACH_FUNCTION_WITH_GIMPLE_BODY (node) + FOR_EACH_FUNCTION (node) if (!node->clone_of && gimple_has_body_p (node->decl)) lto_prepare_function_for_streaming (node);
next prev parent reply other threads:[~2021-04-13 7:55 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-08 10:59 [Bug analyzer/98599] New: " acoplan at gcc dot gnu.org 2021-01-08 16:36 ` [Bug analyzer/98599] " dmalcolm at gcc dot gnu.org 2021-01-08 23:56 ` dmalcolm at gcc dot gnu.org 2021-01-11 12:47 ` marxin at gcc dot gnu.org 2021-01-11 16:29 ` dmalcolm at gcc dot gnu.org 2021-01-12 13:27 ` marxin at gcc dot gnu.org 2021-01-12 23:26 ` dmalcolm at gcc dot gnu.org 2021-01-13 10:31 ` marxin at gcc dot gnu.org 2021-01-13 18:38 ` dmalcolm at gcc dot gnu.org 2021-01-13 22:09 ` dmalcolm at gcc dot gnu.org 2021-03-11 18:04 ` dmalcolm at gcc dot gnu.org 2021-03-31 18:28 ` dmalcolm at gcc dot gnu.org 2021-04-10 17:42 ` [Bug analyzer/98599] [11 Regression] " dmalcolm at gcc dot gnu.org 2021-04-13 1:15 ` cvs-commit at gcc dot gnu.org 2021-04-13 1:16 ` dmalcolm at gcc dot gnu.org 2021-04-13 7:55 ` hubicka at ucw dot cz [this message] 2021-04-13 9:09 ` acoplan at gcc dot gnu.org 2021-04-13 18:26 ` dmalcolm at gcc dot gnu.org 2021-04-15 9:41 ` 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-98599-4-1xuiHQWcar@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: linkBe 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).