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/107937] New: ice in find_var_cmp_const, at gimple-predicate-analysis.cc:257
Date: Wed, 30 Nov 2022 17:17:55 +0000 [thread overview]
Message-ID: <bug-107937-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107937
Bug ID: 107937
Summary: ice in find_var_cmp_const, at
gimple-predicate-analysis.cc:257
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: dcb314 at hotmail dot com
Target Milestone: ---
This reduced C code:
double getk_intersect_line_with_ycylinder_r,
getk_intersect_line_with_ycylinder_a;
getk_intersect_line_with_ycylinder_i;
getk_intersect_line_with_ycylinder(double *k2) {
if (getk_intersect_line_with_ycylinder_r < 0.)
return sqrt(getk_intersect_line_with_ycylinder_r);
*k2 = 0 / getk_intersect_line_with_ycylinder_a;
{
double k2;
for (; getk_intersect_line_with_ycylinder_i;
getk_intersect_line_with_ycylinder_i++)
getk_intersect_line_with_ycylinder(&k2);
vecscale(k2);
}
}
when compiled by recent gcc trunk and compiler flags -O3 -Wall, does this:
during GIMPLE pass: uninit
bug865.c:4:1: internal compiler error: in find_var_cmp_const, at
gimple-predicate-analysis.cc:257
4 | getk_intersect_line_with_ycylinder(double *k2) {
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
0x1b3ad6c find_var_cmp_const(vec<vec<pred_info, va_heap, vl_ptr>, va_heap,
vl_ptr>, gphi*, gimple**, tree_node**)
../../trunk.d1/gcc/gimple-predicate-analysis.cc:257
0x1b3ad6c uninit_analysis::overlap(gphi*, unsigned int, hash_set<gphi*, false,
default_hash_traits<gphi*> >*, predicate const&)
../../trunk.d1/gcc/gimple-predicate-analysis.cc:648
I'll have a go at finding a git range for the problem.
next reply other threads:[~2022-11-30 17:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-30 17:17 dcb314 at hotmail dot com [this message]
2022-11-30 17:19 ` [Bug tree-optimization/107937] [13 Regression] " pinskia at gcc dot gnu.org
2022-11-30 17:23 ` pinskia at gcc dot gnu.org
2022-11-30 17:26 ` pinskia at gcc dot gnu.org
2022-11-30 17:29 ` dcb314 at hotmail dot com
2022-11-30 17:33 ` pinskia at gcc dot gnu.org
2022-12-01 5:24 ` [Bug tree-optimization/107937] [13 Regression] ICE in find_var_cmp_const, at gimple-predicate-analysis.cc:257 since r13-4408-gb628cad9e093f7a3 marxin at gcc dot gnu.org
2022-12-01 5:28 ` marxin at gcc dot gnu.org
2022-12-01 7:34 ` rguenth at gcc dot gnu.org
2022-12-01 8:38 ` zhendong.su at inf dot ethz.ch
2022-12-01 9:54 ` cvs-commit at gcc dot gnu.org
2022-12-01 14:00 ` 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-107937-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: 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).