public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pheeck at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/114628] New: [14 Regression] ICE in gimple_check_failed at gimple.cc:1337 while compiling bitint-100.c
Date: Sun, 07 Apr 2024 10:53:49 +0000	[thread overview]
Message-ID: <bug-114628-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 114628
           Summary: [14 Regression] ICE in gimple_check_failed at
                    gimple.cc:1337 while compiling bitint-100.c
           Product: gcc
           Version: 14.0
            Status: UNCONFIRMED
          Keywords: ice-on-valid-code
          Severity: normal
          Priority: P3
         Component: middle-end
          Assignee: unassigned at gcc dot gnu.org
          Reporter: pheeck at gcc dot gnu.org
  Target Milestone: ---
              Host: x86_64-pc-linux-gnu
            Target: x86_64-pc-linux-gnu

While compiling the gcc.dg/bitint-100.c testsuite testcase

gcc src/gcc/testsuite/gcc.dg/bitint-100.c -fvar-tracking-assignments-toggle

the following ICE occurs

during GIMPLE pass: bitintlower0
src/gcc/testsuite/gcc.dg/bitint-100.c: In function ‘corge’:
src/gcc/testsuite/gcc.dg/bitint-100.c:44:1: internal compiler error: gimple
check: expected gimple_assign(error_mark), have gimple_debug() in
gimple_assign_lhs, at gimple.h:2663
   44 | corge (int x, _BitInt(575) y, _BitInt(325) *z)
      | ^~~~~
0x74f67a gimple_check_failed(gimple const*, char const*, int, char const*,
gimple_code, tree_code)
        /home/fkastl/gcc/src/gcc/gimple.cc:1337
0x1f50114 gassign const* GIMPLE_CHECK2<gassign const*>(gimple const*, char
const*, int, char const*)
        /home/fkastl/gcc/src/gcc/gimple.h:74
0x1f50114 gimple_assign_lhs(gimple const*)
        /home/fkastl/gcc/src/gcc/gimple.h:2663
0x1f50114 gimple_lower_bitint
        /home/fkastl/gcc/src/gcc/gimple-lower-bitint.cc:7195

Compiler configuration (nothing special there I believe):

Reading specs from /home/fkastl/gcc/build/gcc/specs
COLLECT_GCC=/home/fkastl/gcc/build/gcc/xgcc
COLLECT_LTO_WRAPPER=/home/fkastl/gcc/build/gcc/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: /home/fkastl/gcc/src/configure --disable-bootstrap
--enable-checking --disable-libsanitizer --prefix=/home/fkastl/gcc/inst
--enable-languages=c
Thread model: posix
Supported LTO compression algorithms: zlib
gcc version 14.0.1 20240405 (experimental) (GCC)

             reply	other threads:[~2024-04-07 10:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-07 10:53 pheeck at gcc dot gnu.org [this message]
2024-04-07 10:54 ` [Bug middle-end/114628] " pheeck at gcc dot gnu.org
2024-04-07 20:18 ` [Bug middle-end/114628] ICE with _BitInt with computed gotos with returns_twice and -g and optimization pinskia at gcc dot gnu.org
2024-04-08 14:11 ` [Bug middle-end/114628] ICE with _BitInt returns_twice (and computed gotos) with " jakub at gcc dot gnu.org
2024-04-08 14:13 ` jakub at gcc dot gnu.org
2024-04-09  7:29 ` cvs-commit at gcc dot gnu.org
2024-04-09  7:30 ` 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-114628-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).