public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "zhendong.su at inf dot ethz.ch" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/111442] New: ICE on valid code at -O{s,2,3}: Segmentation fault signal terminated program cc1
Date: Sun, 17 Sep 2023 08:55:34 +0000	[thread overview]
Message-ID: <bug-111442-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 111442
           Summary: ICE on valid code at -O{s,2,3}: Segmentation fault
                    signal terminated program cc1
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: tree-optimization
          Assignee: unassigned at gcc dot gnu.org
          Reporter: zhendong.su at inf dot ethz.ch
  Target Milestone: ---

This appears to be a recent regression.

Compiler Explorer: https://godbolt.org/z/TY6sWMvcv

[542] % gcctk -v
Using built-in specs.
COLLECT_GCC=gcctk
COLLECT_LTO_WRAPPER=/local/home/suz/suz-local/software/local/gcc-trunk/bin/../libexec/gcc/x86_64-pc-linux-gnu/14.0.0/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: ../gcc-trunk/configure --disable-bootstrap
--enable-checking=yes --prefix=/local/suz-local/software/local/gcc-trunk
--enable-sanitizers --enable-languages=c,c++ --disable-werror --enable-multilib
Thread model: posix
Supported LTO compression algorithms: zlib
gcc version 14.0.0 20230917 (experimental) (GCC) 
[543] % 
[543] % gcctk -Os small.c
small.c: In function ‘main’:
small.c:5:15: warning: division by zero [-Wdiv-by-zero]
    5 |     e = a ? 0 % 0 : 0;
      |               ^
gcctk: internal compiler error: Segmentation fault signal terminated program
cc1
Please submit a full bug report, with preprocessed source (by using
-freport-bug).
See <https://gcc.gnu.org/bugs/> for instructions.
[544] % 
[544] % cat small.c
int *a, b;
int main() {
  int d = 1, e;
  if (d)
    e = a ? 0 % 0 : 0;
  if (d)
    a = &d;
  d = -1;
  b = d & e;
  b = 2 * e ^ 1;
  return 0;
}

             reply	other threads:[~2023-09-17  8:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-17  8:55 zhendong.su at inf dot ethz.ch [this message]
2023-09-17  9:02 ` [Bug tree-optimization/111442] " pinskia at gcc dot gnu.org
2023-09-17  9:04 ` pinskia at gcc dot gnu.org
2023-09-17  9:05 ` pinskia at gcc dot gnu.org
2023-09-17  9:09 ` [Bug tree-optimization/111442] [14 Regression] " pinskia at gcc dot gnu.org
2023-09-17 21:41 ` pinskia at gcc dot gnu.org
2023-09-18 20:46 ` cvs-commit at gcc dot gnu.org
2023-09-18 20:46 ` 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-111442-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).