public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/106881] New: ice in init_from_control_deps, at gimple-predicate-analysis.cc:1740 Date: Wed, 07 Sep 2022 18:31:41 +0000 [thread overview] Message-ID: <bug-106881-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106881 Bug ID: 106881 Summary: ice in init_from_control_deps, at gimple-predicate-analysis.cc:1740 Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: dcb314 at hotmail dot com Target Milestone: --- Created attachment 53546 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53546&action=edit C source code The attached C code does this: /home/dcb/gcc/results/bin/gcc -c -O1 -Wall -fexceptions bug843.c during GIMPLE pass: uninit src/eap-gtc.c: In function ‘eap_gtc_check_settings’: src/eap-gtc.c:74:12: internal compiler error: in init_from_control_deps, at gimple-predicate-analysis.cc:1740 0x1b161f5 predicate::init_from_control_deps(vec<edge_def*, va_heap, vl_ptr> const*, unsigned int, bool) ../../trunk.git/gcc/gimple-predicate-analysis.cc:1740 0x1b16974 uninit_analysis::init_use_preds(predicate&, basic_block_def*, basic_block_def*) ../../trunk.git/gcc/gimple-predicate-analysis.cc:1996 I will have a go at producing a git range and a reduction.
next reply other threads:[~2022-09-07 18:31 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-07 18:31 dcb314 at hotmail dot com [this message] 2022-09-07 18:41 ` [Bug c/106881] " dcb314 at hotmail dot com 2022-09-07 18:42 ` dcb314 at hotmail dot com 2022-09-07 18:44 ` [Bug tree-optimization/106881] [13 Regression] " pinskia at gcc dot gnu.org 2022-09-07 18:46 ` pinskia at gcc dot gnu.org 2022-09-07 19:29 ` dcb314 at hotmail dot com 2022-09-07 19:34 ` [Bug tree-optimization/106881] [13 Regression] ice in init_from_control_deps, at gimple-predicate-analysis.cc:1740 since r13-2500-g0a4a2667dc115ca7 marxin at gcc dot gnu.org 2022-09-08 9:36 ` rguenth at gcc dot gnu.org 2022-09-08 11:11 ` cvs-commit at gcc dot gnu.org 2022-09-08 11:12 ` rguenth at gcc dot gnu.org 2022-09-08 15:17 ` sbergman at redhat dot com 2022-09-09 7:12 ` dcb314 at hotmail dot com 2022-09-09 8:29 ` marxin at gcc dot gnu.org 2022-09-09 8:39 ` rguenther at suse dot de 2022-09-09 9:48 ` cvs-commit at gcc dot gnu.org 2022-09-09 9: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-106881-4@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).