public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "wbx at openadk dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/111001] New: SH: ICE during RTL pass: sh_treg_combine2
Date: Sat, 12 Aug 2023 09:16:52 +0000	[thread overview]
Message-ID: <bug-111001-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 111001
           Summary: SH: ICE during RTL pass: sh_treg_combine2
           Product: gcc
           Version: 13.2.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: wbx at openadk dot org
  Target Milestone: ---

Created attachment 55731
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55731&action=edit
preprocessed source code of rw_bitmaps.c

Hi,

following compile error occurs for Buildroot targeting sh4-linux-gnu for the
e2fsprogs package:
terminate called after throwing an instance of 'std::bad_alloc'
  what():  std::bad_alloc
during RTL pass: sh_treg_combine2
rw_bitmaps.c: In function ‘read_bitmaps_range_start’:
rw_bitmaps.c:447:1: internal compiler error: Aborted
  447 | }
      | ^
0x7fe95c926f8f ???
        ./signal/../sysdeps/unix/sysv/linux/x86_64/libc_sigaction.c:0
0x7fe95c975ccc __pthread_kill_implementation
        ./nptl/pthread_kill.c:44
0x7fe95c926ef1 __GI_raise
        ../sysdeps/posix/raise.c:26
0x7fe95c911471 __GI_abort
        ./stdlib/abort.c:79
0x7fe95c912189 __libc_start_call_main
        ../sysdeps/nptl/libc_start_call_main.h:58
0x7fe95c912244 __libc_start_main_impl
        ../csu/libc-start.c:381
Please submit a full bug report, with preprocessed source (by using
-freport-bug).
Please include the complete backtrace with any bug report.

Attached is the preprocessed rw_bitmaps.c file.
The problem exist only for -O1/-O2/-O3, using -Os/O0 does not trigger the ICE.
And it is an new issue in gcc 13.2.0, it does not happen for 12.3.0. 

Do you need more information, do not hesitate to ask.
 best regards
  Waldemar

             reply	other threads:[~2023-08-12  9:16 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-12  9:16 wbx at openadk dot org [this message]
2023-08-12  9:17 ` [Bug target/111001] " wbx at openadk dot org
2023-10-13  5:11 ` olegendo at gcc dot gnu.org
2023-10-13  6:03 ` olegendo at gcc dot gnu.org
2023-10-21  4:08 ` olegendo at gcc dot gnu.org
2023-10-22 23:03 ` glaubitz at physik dot fu-berlin.de
2023-10-22 23:04 ` glaubitz at physik dot fu-berlin.de
2023-10-23  0:01 ` olegendo at gcc dot gnu.org
2023-10-23  0:19 ` glaubitz at physik dot fu-berlin.de
2023-10-23  0:21 ` olegendo at gcc dot gnu.org
2023-10-23  7:44 ` glaubitz at physik dot fu-berlin.de
2023-10-23 13:11 ` cvs-commit at gcc dot gnu.org
2023-10-23 13:13 ` cvs-commit at gcc dot gnu.org
2023-10-23 13:21 ` cvs-commit at gcc dot gnu.org
2023-10-23 13:24 ` cvs-commit at gcc dot gnu.org
2023-10-23 13:29 ` olegendo at gcc dot gnu.org
2023-10-23 14:21 ` glaubitz at physik dot fu-berlin.de
2023-10-23 14:53 ` olegendo at gcc dot gnu.org
2024-03-03  6:37 ` olegendo 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-111001-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).