public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "crazylht at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/107193] New: [13 regression] bootstrap error caused by r13-3172-gf30e9fd33e56a5
Date: Sun, 09 Oct 2022 11:37:33 +0000 [thread overview]
Message-ID: <bug-107193-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107193
Bug ID: 107193
Summary: [13 regression] bootstrap error caused by
r13-3172-gf30e9fd33e56a5
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: bootstrap
Assignee: unassigned at gcc dot gnu.org
Reporter: crazylht at gmail dot com
Target Milestone: ---
Created attachment 53683
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53683&action=edit
_sd_to_udi.i
export/users2/liuhongt/tools-build/build_git_trunk_master_native_bootstrap/./gcc/xgcc
-B/export/users2/liuhongt/tools-build/build_git_trunk_master_native_bootstrap/./gcc/
-B/export/users2/liuhongt/install/git_trunk_master_native_bootstrap/x86_64-pc-linux-gnu/bin/
-B/export/users2/liuhongt/install/git_trunk_master_native_bootstrap/x86_64-pc-linux-gnu/lib/
-isystem
/export/users2/liuhongt/install/git_trunk_master_native_bootstrap/x86_64-pc-linux-gnu/include
-isystem
/export/users2/liuhongt/install/git_trunk_master_native_bootstrap/x86_64-pc-linux-gnu/sys-include
-fno-checking -g -O2 -m32 -O2 -g -O2 -DIN_GCC -W -Wall -Wno-narrowing
-Wwrite-strings -Wcast-qual -Wstrict-prototypes -Wmissing-prototypes
-Wold-style-definition -isystem ./include -fpic -mlong-double-80
-DUSE_ELF_SYMVER -fcf-protection -mshstk -g -DIN_LIBGCC2 -fbuilding-libgcc
-fno-stack-protector -fpic -mlong-double-80 -DUSE_ELF_SYMVER -fcf-protection
-mshstk -I. -I. -I../../.././gcc
-I/export/users2/liuhongt/gcc/git_trunk/master/libgcc
-I/export/users2/liuhongt/gcc/git_trunk/master/libgcc/.
-I/export/users2/liuhongt/gcc/git_trunk/master/libgcc/../gcc
-I/export/users2/liuhongt/gcc/git_trunk/master/libgcc/../include
-I/export/users2/liuhongt/gcc/git_trunk/master/libgcc/config/libbid
-DENABLE_DECIMAL_BID_FORMAT -DHAVE_CC_TLS -DUSE_TLS -o _sd_to_udi.o -MT
_sd_to_udi.o -MD -MP -MF _sd_to_udi.dep -DFINE_GRAINED_LIBRARIES -DL_sd_to_udi
-DWIDTH=32 -c
/export/users2/liuhongt/gcc/git_trunk/master/libgcc/config/libbid/_sd_to_udi.c
during GIMPLE pass: cfg
/export/users2/liuhongt/gcc/git_trunk/master/libgcc/config/libbid/_sd_to_udi.c:
In function ‘__bid_fixunssddi’:
/export/users2/liuhongt/gcc/git_trunk/master/libgcc/config/libbid/_sd_to_udi.c:29:1:
internal compiler error: Segmentation fault
29 | __bid_fixunssddi (_Decimal32 x) {
| ^~~~~~~~~~~~~~~~
Please submit a full bug report, with preprocessed source (by using
-freport-bug).
See <https://gcc.gnu.org/bugs/> for instructions.
make[5]: *** [Makefile:722: _sd_to_udi.o] Error 1
make[5]: Leaving directory
'/export/users2/liuhongt/tools-build/build_git_trunk_master_native_bootstrap/x86_64-pc-linux-gnu/32/libgcc'
make[4]: *** [Makefile:1214: multi-do] Error 1
make[4]: Leaving directory
'/export/users2/liuhongt/tools-build/build_git_trunk_master_native_bootstrap/x86_64-pc-linux-gnu/libgcc'
make[3]: *** [Makefile:127: all-multi] Error 2
make[3]: Leaving directory
'/export/users2/liuhongt/tools-build/build_git_trunk_master_native_bootstrap/x86_64-pc-linux-gnu/libgcc'
make[2]: *** [Makefile:24226: all-stage2-target-libgcc] Error 2
make[2]: Leaving directory
'/export/users2/liuhongt/tools-build/build_git_trunk_master_native_bootstrap'
make[1]: *** [Makefile:30117: stage2-bubble] Error 2
make[1]: Leaving directory
'/export/users2/liuhongt/tools-build/build_git_trunk_master_native_bootstrap'
make: *** [Makefile:1071: all] Error 2
reproduce with attached testcase
./gcc/xgcc -B ./gcc -O2 _sd_to_udi.i -g -m32
And It looks like there's some random when reproducing.(sometimes pass,
sometimes failed).
next reply other threads:[~2022-10-09 11:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-09 11:37 crazylht at gmail dot com [this message]
2022-10-09 18:52 ` [Bug bootstrap/107193] " pinskia at gcc dot gnu.org
2022-10-09 18:52 ` [Bug debug/107193] " pinskia at gcc dot gnu.org
2022-10-10 7:22 ` rguenth at gcc dot gnu.org
2022-10-10 7:28 ` crazylht at gmail dot com
2022-10-10 8:18 ` crazylht at gmail dot com
2022-10-10 8:29 ` crazylht at gmail dot com
2022-10-10 13:28 ` marxin at gcc dot gnu.org
2022-10-10 20:49 ` erozen at microsoft dot com
2022-10-10 22:42 ` hjl.tools at gmail dot com
2022-10-10 22:45 ` hjl.tools at gmail dot com
2022-10-10 23:00 ` erozen at microsoft dot com
2022-10-11 2:51 ` erozen at microsoft dot com
2022-10-11 6:35 ` cvs-commit at gcc dot gnu.org
2022-10-11 7:11 ` marxin 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-107193-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).