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++/109274] New: ice in in_chain_p, at gimple-range-gori.cc:119
Date: Fri, 24 Mar 2023 12:23:38 +0000	[thread overview]
Message-ID: <bug-109274-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 109274
           Summary: ice in in_chain_p, at gimple-range-gori.cc:119
           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 C++ code:

float mulsignf_cb, mulsignf_t, mulsignf_bpa;
int mulsignf___trans_tmp_1;
float mulsignf() {
  mulsignf_cb = 0 * -(2.0f * mulsignf_bpa);
  mulsignf___trans_tmp_1 = mulsignf_cb != mulsignf_cb ? 0 : mulsignf();
  mulsignf_t = mulsignf_bpa;
}

when compiled by recent g++ trunk and flag -O2, does this:

bug902.cc: In function ‘float mulsignf()’:
bug902.cc:7:1: warning: no return statement in function returning non-void
[-Wre
turn-type]
    7 | }
      | ^
during GIMPLE pass: vrp
bug902.cc:3:7: internal compiler error: in in_chain_p, at
gimple-range-gori.cc:1
19
    3 | float mulsignf() {
      |       ^~~~~~~~
0x92e285 range_def_chain::in_chain_p(tree_node*, tree_node*)
        ../../trunk.year/gcc/gimple-range-gori.cc:119
0x1fd69f4 gori_compute::compute_operand_range(vrange&, gimple*, vrange const&,
t
ree_node*, fur_source&, value_relation*)
        ../../trunk.year/gcc/gimple-range-gori.cc:667

The bug first seems to appear sometime from git hash g:454a4d5041f53cd1 to
g:0963cb5fde158cce, a distance of 41 commits.

             reply	other threads:[~2023-03-24 12:23 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-24 12:23 dcb314 at hotmail dot com [this message]
2023-03-24 12:30 ` [Bug tree-optimization/109274] [13 Regression] ice in in_chain_p, at gimple-range-gori.cc:119 starting with r13-6787 jakub at gcc dot gnu.org
2023-03-24 12:48 ` [Bug tree-optimization/109274] [13 Regression] ice in in_chain_p, at gimple-range-gori.cc:119 starting with r13-6787-g0963cb5fde158cce986 rguenth at gcc dot gnu.org
2023-03-24 13:33 ` jakub at gcc dot gnu.org
2023-03-24 14:27 ` jakub at gcc dot gnu.org
2023-03-24 14:28 ` jakub at gcc dot gnu.org
2023-03-24 15:02 ` amacleod at redhat dot com
2023-03-24 15:10 ` jakub at gcc dot gnu.org
2023-03-27  7:46 ` slyfox at gcc dot gnu.org
2023-03-27  8:11 ` marxin at gcc dot gnu.org
2023-03-27  8:49 ` jakub at gcc dot gnu.org
2023-03-27 14:10 ` amacleod at redhat dot com
2023-03-28  3:05 ` amacleod at redhat dot com
2023-03-28 13:34 ` cvs-commit at gcc dot gnu.org
2023-03-28 13:35 ` amacleod at redhat dot com
2023-03-29  1:42 ` sam at gentoo dot 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-109274-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).