public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/96130] [10/11 Regression] ICE in analyze_function_body at gcc/ipa-fnsummary.c:2769 since r10-3199-g351e7c3b5fbd45bd
Date: Fri, 10 Jul 2020 14:13:41 +0000	[thread overview]
Message-ID: <bug-96130-4-68OymIzJKZ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96130-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
My understanding of the problem is that set_switch_stmt_execution_predicate
figures out that the default: is unreachable (operand is a bitfield with values
0 to 7 and there are cases for all 8) and notes that into the predicate for the
switch -> default: edge's aux, and then compute_bb_predicates iterates, but as
the 3 -> 9 predicate always resolves to false, nothing adds bb_9->aux.  And
later we try to dereference that.
So, either predicates in bb->aux are optional and we should treat a missing
predicate as false predicate, or compute_bb_predicate should ensure to fill in
bb->aux even for bbs it left NULL at the end.
          if (bb->aux)
            bb_predicate = *(predicate *) bb->aux;
          else
            bb_predicate = false;
in analyze_function_body suggests that perhaps the latter is the case.

  parent reply	other threads:[~2020-07-10 14:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-09  8:33 [Bug c/96130] New: 10.1.1: segfault during IPA pass: fnsummary manuel.lauss at googlemail dot com
2020-07-09  8:37 ` [Bug c/96130] " marxin at gcc dot gnu.org
2020-07-09  8:45 ` [Bug ipa/96130] [10/11 Regression] ICE in analyze_function_body at gcc/ipa-fnsummary.c:2769 since r10-3199-g351e7c3b5fbd45bd marxin at gcc dot gnu.org
2020-07-09  8:56 ` marxin at gcc dot gnu.org
2020-07-09 11:37 ` rguenth at gcc dot gnu.org
2020-07-10 13:38 ` marxin at gcc dot gnu.org
2020-07-10 13:47 ` jakub at gcc dot gnu.org
2020-07-10 14:13 ` jakub at gcc dot gnu.org [this message]
2020-07-10 14:18 ` jakub at gcc dot gnu.org
2020-07-11 13:25 ` jakub at gcc dot gnu.org
2020-07-13 16:27 ` cvs-commit at gcc dot gnu.org
2020-07-13 16:31 ` cvs-commit at gcc dot gnu.org
2020-07-13 16:34 ` jakub 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-96130-4-68OymIzJKZ@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).