public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/106189] [10/11/12/13 Regression] ICE: Floating point exception since r9-1948-gd893b683f40884cd
Date: Thu, 07 Jul 2022 12:40:14 +0000 [thread overview]
Message-ID: <bug-106189-4-Y6GQR0eeRt@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106189-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106189
--- Comment #2 from Martin Liška <marxin at gcc dot gnu.org> ---
Reduced test-case:
$ cat warray-bounds.c
a_n_0_0_a[][0];
a_n_0_0() { T(((char *)a_n_0_0_a)[1]); }
$ gcc warray-bounds.c -c -O2 -Warray-bounds=2 -w
during GIMPLE pass: vrp
warray-bounds.c: In function ‘a_n_0_0’:
warray-bounds.c:2:1: internal compiler error: Floating point exception
2 | a_n_0_0() { T(((char *)a_n_0_0_a)[1]); }
| ^~~~~~~
0xf59efa crash_signal
/home/marxin/Programming/gcc/gcc/toplev.cc:322
0x7ffff78567bf ???
/usr/src/debug/glibc-2.35-5.1.x86_64/signal/../sysdeps/unix/sysv/linux/x86_64/libc_sigaction.c:0
0x1d1b484 array_bounds_checker::check_mem_ref(unsigned int, tree_node*, bool)
/home/marxin/Programming/gcc/gcc/gimple-array-bounds.cc:537
0x1d1baf9 array_bounds_checker::check_array_bounds(tree_node**, int*, void*)
/home/marxin/Programming/gcc/gcc/gimple-array-bounds.cc:727
0x12662cb walk_tree_1(tree_node**, tree_node* (*)(tree_node**, int*, void*),
void*, hash_set<tree_node*, false, default_hash_traits<tree_node*> >*,
tree_node* (*)(tree_node**, int*, tree_node* (*)(tree_node**, int*, void*),
void*, hash_set<tree_node*, false, default_hash_traits<tree_node*> >*))
/home/marxin/Programming/gcc/gcc/tree.cc:11237
0xc4d120 walk_gimple_op(gimple*, tree_node* (*)(tree_node**, int*, void*),
walk_stmt_info*)
/home/marxin/Programming/gcc/gcc/gimple-walk.cc:202
0x1d19a5a check_array_bounds_dom_walker::before_dom_children(basic_block_def*)
/home/marxin/Programming/gcc/gcc/gimple-array-bounds.cc:790
0x1d02fe5 dom_walker::walk(basic_block_def*)
/home/marxin/Programming/gcc/gcc/domwalk.cc:311
0x1d19c9b array_bounds_checker::check()
/home/marxin/Programming/gcc/gcc/gimple-array-bounds.cc:804
0x123e421 execute_vrp
/home/marxin/Programming/gcc/gcc/tree-vrp.cc:4235
Please submit a full bug report, with preprocessed source (by using
-freport-bug).
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.
next prev parent reply other threads:[~2022-07-07 12:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-04 19:39 [Bug c/106189] New: [10/11/12/13 Regression] ICE: Floating point exception gscfq@t-online.de
2022-07-04 20:14 ` [Bug tree-optimization/106189] " pinskia at gcc dot gnu.org
2022-07-07 12:37 ` [Bug tree-optimization/106189] [10/11/12/13 Regression] ICE: Floating point exception since r9-1948-gd893b683f40884cd marxin at gcc dot gnu.org
2022-07-07 12:40 ` marxin at gcc dot gnu.org [this message]
2022-07-25 15:23 ` rguenth at gcc dot gnu.org
2022-07-26 6:37 ` cvs-commit at gcc dot gnu.org
2022-07-27 9:24 ` [Bug tree-optimization/106189] [10/11/12 " cvs-commit at gcc dot gnu.org
2022-10-17 13:28 ` [Bug tree-optimization/106189] [10/11 " cvs-commit at gcc dot gnu.org
2023-07-07 10:02 ` [Bug tree-optimization/106189] [10 " 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-106189-4-Y6GQR0eeRt@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).