public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "zsojka at seznam dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/113119] ICE: verify_ssa failed: definition in block 18 does not dominate use in block 4 at -O1 with _BitInt
Date: Sat, 23 Dec 2023 07:41:48 +0000	[thread overview]
Message-ID: <bug-113119-4-UkxHmQE23z@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113119-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Zdenek Sojka <zsojka at seznam dot cz> ---
Created attachment 56925
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56925&action=edit
slightly less reduced testcase, ICEing elsewhere

The original testcase was ICEing at a different place, as does this testcase:

$ x86_64-pc-linux-gnu-gcc -O testcase.c 
during GIMPLE pass: bitintlower
testcase.c: In function 'foo':
testcase.c:8:1: internal compiler error: in operator[], at vec.h:910
    8 | foo(_BitInt(4058) d)
      | ^~~
0x8a0a88 vec<tree_node*, va_gc, vl_embed>::operator[](unsigned int)
        /repo/gcc-trunk/gcc/vec.h:910
0x8a0c6e vec<equiv_chain*, va_heap, vl_embed>::operator[](unsigned int)
        /repo/gcc-trunk/gcc/value-relation.cc:736
0x8a0c6e vec<equiv_chain*, va_heap, vl_ptr>::operator[](unsigned int)
        /repo/gcc-trunk/gcc/vec.h:1599
0x8a0c6e equiv_oracle::add_equiv_to_block(basic_block_def*, bitmap_head*)
        /repo/gcc-trunk/gcc/value-relation.cc:721
0x185e5c2 equiv_oracle::register_relation(basic_block_def*, relation_kind_t,
tree_node*, tree_node*)
        /repo/gcc-trunk/gcc/value-relation.cc:675
0x26597e9 fold_using_range::range_of_range_op(vrange&,
gimple_range_op_handler&, fur_source&)
        /repo/gcc-trunk/gcc/gimple-range-fold.cc:687
0x2659bf2 fold_using_range::fold_stmt(vrange&, gimple*, fur_source&,
tree_node*)
        /repo/gcc-trunk/gcc/gimple-range-fold.cc:602
0x2641c7e gimple_ranger::fold_range_internal(vrange&, gimple*, tree_node*)
        /repo/gcc-trunk/gcc/gimple-range.cc:265
0x2641c7e gimple_ranger::range_of_stmt(vrange&, gimple*, tree_node*)
        /repo/gcc-trunk/gcc/gimple-range.cc:326
0x264597a gimple_ranger::range_of_expr(vrange&, tree_node*, gimple*)
        /repo/gcc-trunk/gcc/gimple-range.cc:134
0x261e312 range_to_prec
        /repo/gcc-trunk/gcc/gimple-lower-bitint.cc:1980
0x2620acb handle_operand_addr
        /repo/gcc-trunk/gcc/gimple-lower-bitint.cc:2025
0x26217e7 lower_muldiv_stmt
        /repo/gcc-trunk/gcc/gimple-lower-bitint.cc:3365
0x2635599 gimple_lower_bitint
        /repo/gcc-trunk/gcc/gimple-lower-bitint.cc:6490
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.

  parent reply	other threads:[~2023-12-23  7:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-22 18:54 [Bug tree-optimization/113119] New: " zsojka at seznam dot cz
2023-12-22 21:04 ` [Bug tree-optimization/113119] " jakub at gcc dot gnu.org
2023-12-23  7:41 ` zsojka at seznam dot cz [this message]
2023-12-23  9:50 ` jakub at gcc dot gnu.org
2024-01-08 13:00 ` cvs-commit at gcc dot gnu.org
2024-01-08 13:02 ` jakub 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-113119-4-UkxHmQE23z@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).