public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sjames at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/109477] New: [13 regression] ICE: internal compiler error: verify_flow_info failed (error: returns_twice call is not first in basic block 8) when building busybox
Date: Tue, 11 Apr 2023 20:13:24 +0000 [thread overview]
Message-ID: <bug-109477-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109477
Bug ID: 109477
Summary: [13 regression] ICE: internal compiler error:
verify_flow_info failed (error: returns_twice call is
not first in basic block 8) when building busybox
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: sjames at gcc dot gnu.org
Target Milestone: ---
Host: x86_64-pc-linux-gnu
Target: x86_64-pc-linux-gnu
Build: x86_64-pc-linux-gnu
Created attachment 54832
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54832&action=edit
wget.i.orig
Hit this when building busybox-1.34.1 w/ 13.0.1 20230409 with checking.
```
x86_64-pc-linux-gnu-gcc -Wp,-MD,networking/.wget.o.d -std=gnu99 -Iinclude
-Ilibbb -include include/autoconf.h -D_GNU_SOURCE -DNDEBUG -D_LARGEFILE_SOURCE
-D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -DBB_VER='"1.34.1"' -O2 -pipe
-march=native -fdiagnostics-color=always -frecord-gcc-switches -Wreturn-type
-fno-strict-aliasing -Wall -Wshadow -Wwrite-strings -Wundef -Wstrict-prototypes
-Wunused -Wunused-parameter -Wunused-function -Wunused-value
-Wmissing-prototypes -Wmissing-declarations -Wno-format-security
-Wdeclaration-after-statement -Wold-style-definition -finline-limit=0
-fno-builtin-strlen -ffunction-sections -fdata-sections
-fno-guess-branch-probability -funsigned-char -fno-unwind-tables
-fno-asynchronous-unwind-tables -fno-builtin-printf
-DKBUILD_BASENAME='"wget"' -DKBUILD_MODNAME='"wget"' -c -o networking/wget.o
networking/wget.c
networking/wget.c: In function ‘spawn_https_helper_openssl’:
networking/wget.c:666:12: error: returns_twice call is not first in basic block
8
666 | static int spawn_https_helper_openssl(const char *host, unsigned port)
| ^~~~~~~~~~~~~~~~~~~~~~~~~~
bb__xvfork_pid_45 = vfork ();
during GIMPLE pass: slp
networking/wget.c:666:12: internal compiler error: verify_flow_info failed
0x7acafb verify_flow_info()
/usr/src/debug/sys-devel/gcc-13.0.1_pre20230409-r1/gcc-13-20230409/gcc/cfghooks.cc:285
0x1523abd execute_function_todo
/usr/src/debug/sys-devel/gcc-13.0.1_pre20230409-r1/gcc-13-20230409/gcc/passes.cc:2110
0x1489c51 do_per_function
/usr/src/debug/sys-devel/gcc-13.0.1_pre20230409-r1/gcc-13-20230409/gcc/passes.cc:1694
0x1489c51 execute_todo
/usr/src/debug/sys-devel/gcc-13.0.1_pre20230409-r1/gcc-13-20230409/gcc/passes.cc:2152
Please submit a full bug report, with preprocessed source (by using
-freport-bug).
Please include the complete backtrace with any bug report.
See <https://bugs.gentoo.org/> for instructions.
```
next reply other threads:[~2023-04-11 20:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-11 20:13 sjames at gcc dot gnu.org [this message]
2023-04-11 20:13 ` [Bug tree-optimization/109477] " sjames at gcc dot gnu.org
2023-04-11 20:14 ` sjames at gcc dot gnu.org
2023-04-11 20:16 ` sjames at gcc dot gnu.org
2023-04-12 6:05 ` amonakov 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-109477-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).