public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "urs at akk dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug analyzer/107711] New: internal compiler error: Segmentation fault
Date: Wed, 16 Nov 2022 00:33:19 +0000 [thread overview]
Message-ID: <bug-107711-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107711
Bug ID: 107711
Summary: internal compiler error: Segmentation fault
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: analyzer
Assignee: dmalcolm at gcc dot gnu.org
Reporter: urs at akk dot org
Target Milestone: ---
Host: x86_64-pc-linux-gnu
Target: x86_64-pc-linux-gnu
Build: x86_64-pc-linux-gnu
Created attachment 53904
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53904&action=edit
internal compiler error: Segmentation fault
gcc build from git @ 6052482f841634522c6d2e56c4231f8df2dc6d3e
with
configure --program-suffix=-13 --enable-languages=c,lto --enable-lto
--disable-multilib
make -j 4 BOOT_CFLAGS='-pipe -O0 -w' bootstrap
on x86_64-pc-linux-gnu (Intel(R) Core(TM) i7-6700T); Ubuntu 22.04.1 LTS; GLIBC
2.35-0ubuntu3.1
gcc-13 -I. -I../include -DHAVE_CONFIG_H -DDEBUG -g -std=c11 -O2 -Wextra
-Wpedantic -Wall -Winline -Wshadow -Wstrict-prototypes -Wmissing-prototypes
-Wmissing-declarations -Wbad-function-cast -Wnested-externs -Wcast-align
-Wpointer-arith -Waggregate-return -Wcast-qual -Wwrite-strings -Wundef -Wpacked
-Wfloat-equal -Wunused-macros -Wold-style-definition -Winit-self
-Wmissing-include-dirs -Wlogical-op -Wjump-misses-init -Wformat=2
-Wshift-overflow=2 -Wnull-dereference -Wduplicated-cond -Walloc-zero -Walloca
-Wstringop-overflow=2 -Wduplicated-branches -Wno-format-nonliteral
-Wno-stringop-truncation -Wno-format-truncation -fanalyzer -o makecfg
./makecfg.c
results in
./makecfg.c: At top level:
./makecfg.c:552:1: internal compiler error: Segmentation fault
552 | }
| ^
0x7feba1f0151f ???
./signal/../sysdeps/unix/sysv/linux/x86_64/libc_sigaction.c:0
0x7feba1ee8d8f __libc_start_call_main
../sysdeps/nptl/libc_start_call_main.h:58
0x7feba1ee8e3f __libc_start_main_impl
../csu/libc-start.c:392
Please submit a full bug report, with preprocessed source (by using
-freport-bug).
I can't see the issue with additional "-v -save-temps -freport-bug" or without
"-fanalyzer".
next reply other threads:[~2022-11-16 0:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-16 0:33 urs at akk dot org [this message]
2022-11-16 14:41 ` [Bug analyzer/107711] " dmalcolm at gcc dot gnu.org
2022-11-16 15:26 ` urs at akk dot org
2022-11-16 15:50 ` dmalcolm at gcc dot gnu.org
2022-11-16 15:54 ` dmalcolm at gcc dot gnu.org
2022-11-16 19:41 ` urs at akk dot org
2022-11-16 19:50 ` urs at akk dot org
2022-11-16 21:15 ` [Bug analyzer/107711] ICE with -fanalyzer with -Wunused-macros since r13-4073-gd8aba860b34203 dmalcolm at gcc dot gnu.org
2022-11-16 22:45 ` [Bug analyzer/107711] [13 Regression] ICE with "-fanalyzer -Wunused-macros" " cvs-commit at gcc dot gnu.org
2022-11-16 23:18 ` dmalcolm at gcc dot gnu.org
2022-11-17 3:07 ` dmalcolm at gcc dot gnu.org
2022-11-17 17:36 ` cvs-commit at gcc dot gnu.org
2022-11-17 17:36 ` dmalcolm at gcc dot gnu.org
2022-11-28 22:24 ` 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-107711-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).