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/109695] New: crash in gimple_ranger::range_of_expr Date: Tue, 02 May 2023 09:57:37 +0000 [thread overview] Message-ID: <bug-109695-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109695 Bug ID: 109695 Summary: crash in gimple_ranger::range_of_expr 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: --- Created attachment 54966 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54966&action=edit gzipped C++ source code The attached C++ code does this when compiled by today's gcc: $ ~/gcc/results.20230502.asan.ubsan/bin/gcc -c -w bug914.cc gcc: internal compiler error: Segmentation fault signal terminated program cc1plus Please submit a full bug report, with preprocessed source (by using -freport-bug). See <https://gcc.gnu.org/bugs/> for instructions. $ It was fine yesterday: $ ~/gcc/results.20230501.asan.ubsan/bin/gcc -c -w bug914.cc $ Here is a stack backtrace of the crash: #0 0x0000000001f5328b in gimple_ranger::range_of_expr (this=0x36e4d50, r=..., expr=0x7fffe0369990, stmt=0x7fffe8cd6688) at ../../trunk.year/gcc/gimple-range.cc:87 #1 0x0000000001f62f96 in fold_using_range::range_of_range_op ( this=this@entry=0x7ffffc01e100, r=..., handler=..., src=...) at ../../trunk.year/gcc/gimple-range-fold.cc:559 #2 0x0000000001f61d4e in fold_using_range::fold_stmt (this=0x7ffffc01e100, r=..., s=0x7fffe8cd6688, src=..., name=0x7fffe0369cf0) at ../../trunk.year/gcc/gimple-range-fold.cc:490 #3 0x0000000001f54220 in gimple_ranger::fold_range_internal (this=0x36e4d50, r=..., s=0x7fffe8cd6688, name=<optimized out>) at ../../trunk.year/gcc/gimple-range.cc:257
next reply other threads:[~2023-05-02 9:57 UTC|newest] Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-02 9:57 dcb314 at hotmail dot com [this message] 2023-05-02 10:44 ` [Bug c/109695] " dcb314 at hotmail dot com 2023-05-02 11:06 ` dcb314 at hotmail dot com 2023-05-02 12:15 ` [Bug tree-optimization/109695] [14 Regression] " rguenth at gcc dot gnu.org 2023-05-02 13:43 ` aldyh at gcc dot gnu.org 2023-05-02 13:43 ` aldyh at gcc dot gnu.org 2023-05-02 14:35 ` aldyh at gcc dot gnu.org 2023-05-02 15:02 ` amacleod at redhat dot com 2023-05-02 16:52 ` aldyh at gcc dot gnu.org 2023-05-02 20:37 ` amacleod at redhat dot com 2023-05-03 8:02 ` mikael at gcc dot gnu.org 2023-05-03 10:54 ` marxin at gcc dot gnu.org 2023-05-03 12:13 ` [Bug tree-optimization/109695] [14 Regression] crash in gimple_ranger::range_of_expr since r14-377-gc92b8be9b52b7e jakub at gcc dot gnu.org 2023-05-03 12:14 ` jakub at gcc dot gnu.org 2023-05-03 12:20 ` jakub at gcc dot gnu.org 2023-05-03 13:02 ` aldyh at gcc dot gnu.org 2023-05-03 13:06 ` jakub at gcc dot gnu.org 2023-05-03 14:31 ` amacleod at redhat dot com 2023-05-04 5:51 ` aldyh at gcc dot gnu.org 2023-05-04 9:02 ` jakub at gcc dot gnu.org 2023-05-04 9:06 ` sjames at gcc dot gnu.org 2023-05-04 9:52 ` rguenther at suse dot de 2023-05-04 16:01 ` dcb314 at hotmail dot com 2023-05-04 16:14 ` dcb314 at hotmail dot com 2023-05-04 16:22 ` amacleod at redhat dot com 2023-05-09 12:00 ` aldyh at gcc dot gnu.org 2023-05-09 12:36 ` aldyh at gcc dot gnu.org 2023-05-09 13:01 ` rguenth at gcc dot gnu.org 2023-05-09 13:03 ` jakub at gcc dot gnu.org 2023-05-09 13:28 ` rguenther at suse dot de 2023-05-09 14:24 ` aldyh at gcc dot gnu.org 2023-05-09 14:35 ` jakub at gcc dot gnu.org 2023-05-09 15:02 ` aldyh at gcc dot gnu.org 2023-05-09 15:13 ` jakub at gcc dot gnu.org 2023-05-10 6:48 ` rguenther at suse dot de 2023-05-10 15:03 ` jakub at gcc dot gnu.org 2023-05-11 4:22 ` aldyh at gcc dot gnu.org 2023-05-11 4:31 ` aldyh at gcc dot gnu.org 2023-05-15 17:23 ` cvs-commit at gcc dot gnu.org 2023-05-23 21:49 ` amacleod at redhat dot com 2023-05-24 5:46 ` aldyh at gcc dot gnu.org 2023-05-24 12:41 ` cvs-commit at gcc dot gnu.org 2023-05-24 12:41 ` cvs-commit at gcc dot gnu.org 2023-05-24 12:41 ` cvs-commit at gcc dot gnu.org 2023-05-24 14:04 ` amacleod at redhat dot com
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-109695-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).