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/112941] during GIMPLE pass: bitintlower ICE: in handle_operand_addr, at gimple-lower-bitint.cc:2126 (gimple-lower-bitint.cc:2134) at -O with _BitInt()
Date: Wed, 13 Dec 2023 20:03:47 +0000	[thread overview]
Message-ID: <bug-112941-4-e1uxuCh7d7@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112941-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Zdenek Sojka <zsojka at seznam dot cz> ---
(In reply to Andrew Pinski from comment #1)
> Confirmed.
> 
> Slightly more reduced:
> ```
> _BitInt (2049) b2049;
> unsigned _BitInt (6384) b16384;
> 
> void
> foo (signed char t)
> {
>   b2049 = b16384 * t;
> }
> 
> ```

Thank you for the further reduction.
In the original testcase, foo() and bar() trigger different ICE ( :2126 and
:2134 )

  parent reply	other threads:[~2023-12-13 20:03 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-09 14:26 [Bug tree-optimization/112941] New: " zsojka at seznam dot cz
2023-12-09 23:39 ` [Bug tree-optimization/112941] " pinskia at gcc dot gnu.org
2023-12-13 20:03 ` zsojka at seznam dot cz [this message]
2023-12-14 15:41 ` jakub at gcc dot gnu.org
2023-12-15 10:19 ` jakub at gcc dot gnu.org
2023-12-15 11:07 ` jakub at gcc dot gnu.org
2023-12-15 12:33 ` jakub at gcc dot gnu.org
2023-12-20 10:34 ` cvs-commit at gcc dot gnu.org
2023-12-20 13:20 ` jakub at gcc dot gnu.org
2023-12-20 14:42 ` jakub at gcc dot gnu.org
2023-12-21 10:14 ` cvs-commit at gcc dot gnu.org
2023-12-21 16:50 ` jakub at gcc dot gnu.org
2023-12-22 11:30 ` cvs-commit at gcc dot gnu.org
2024-01-03  9:17 ` jakub at gcc dot gnu.org
2024-01-20 17:11 ` pinskia 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-112941-4-e1uxuCh7d7@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).