public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pkubaj at anongoth dot pl" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/89494] Bootstrap error when using GCC 4.2.1 Date: Fri, 01 May 2020 01:36:55 +0000 [thread overview] Message-ID: <bug-89494-4-MoLazAbVlB@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-89494-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89494 Piotr Kubaj <pkubaj at anongoth dot pl> changed: What |Removed |Added ---------------------------------------------------------------------------- Version|9.3.0 |10.0 --- Comment #25 from Piotr Kubaj <pkubaj at anongoth dot pl> --- Happens on 20200419 snapshot: gmake[4]: Entering directory '/wrkdirs/usr/ports/lang/gcc10-devel/work/.build/libiberty' if [ x"-fPIC" != x ]; then \ /wrkdirs/usr/ports/lang/gcc10-devel/work/.build/./prev-gcc/xgcc -B/wrkdirs/usr/ports/lang/gcc10-devel/work/.build/./prev-gcc/ -B/usr/local/powerpc64-portbld-freebsd12.1/bin/ -B/usr/local/powerpc64-portbld-freebsd12.1/bin/ -B/usr/local/powerpc64-portbld-freebsd12.1/lib/ -isystem /usr/local/powerpc64-portbld-freebsd12.1/include -isystem /usr/local/powerpc64-portbld-freebsd12.1/sys-include -fno-checking -c -DHAVE_CONFIG_H -O0 -fno-checking -gtoggle -DLIBICONV_PLUG -I. -I/wrkdirs/usr/ports/lang/gcc10-devel/work/gcc-10-20200419/libiberty/../include -W -Wall -Wwrite-strings -Wc++-compat -Wstrict-prototypes -Wshadow=local -pedantic -D_GNU_SOURCE -fPIC /wrkdirs/usr/ports/lang/gcc10-devel/work/gcc-10-20200419/libiberty/regex.c -o pic/regex.o; \ else true; fi during RTL pass: reload In file included from /wrkdirs/usr/ports/lang/gcc10-devel/work/gcc-10-20200419/libiberty/regex.c:639: /wrkdirs/usr/ports/lang/gcc10-devel/work/gcc-10-20200419/libiberty/regex.c: In function 'byte_regex_compile': /wrkdirs/usr/ports/lang/gcc10-devel/work/gcc-10-20200419/libiberty/regex.c:4223:1: internal compiler error: Segmentation fault 4223 | } /* regex_compile */ | ^ no stack trace because unwind library not available Please submit a full bug report, with preprocessed source if appropriate. See <https://gcc.gnu.org/bugs/> for instructions. gmake[4]: *** [Makefile:1179: regex.o] Error 1 gmake[4]: Leaving directory '/wrkdirs/usr/ports/lang/gcc10-devel/work/.build/libiberty' gmake[3]: *** [Makefile:11311: all-stage2-libiberty] Error 2 gmake[3]: Leaving directory '/wrkdirs/usr/ports/lang/gcc10-devel/work/.build' gmake[2]: *** [Makefile:23020: stage2-bubble] Error 2 gmake[2]: Leaving directory '/wrkdirs/usr/ports/lang/gcc10-devel/work/.build' gmake[1]: *** [Makefile:23235: bootstrap-lean] Error 2 gmake[1]: Leaving directory '/wrkdirs/usr/ports/lang/gcc10-devel/work/.build' *** Error code 1
next prev parent reply other threads:[~2020-05-01 1:36 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-89494-4@http.gcc.gnu.org/bugzilla/> 2020-04-11 3:15 ` pkubaj at anongoth dot pl 2020-04-11 18:02 ` pkubaj at anongoth dot pl 2020-04-11 18:08 ` pkubaj at anongoth dot pl 2020-04-12 11:18 ` pkubaj at anongoth dot pl 2020-04-12 15:54 ` pkubaj at anongoth dot pl 2020-04-14 20:36 ` jakub at gcc dot gnu.org 2020-04-14 21:08 ` iains at gcc dot gnu.org 2020-04-14 21:13 ` jakub at gcc dot gnu.org 2020-04-15 12:20 ` jakub at gcc dot gnu.org 2020-04-15 13:17 ` cvs-commit at gcc dot gnu.org 2020-04-15 13:42 ` pkubaj at anongoth dot pl 2020-04-15 14:46 ` jakub at gcc dot gnu.org 2020-04-16 8:16 ` cvs-commit at gcc dot gnu.org 2020-05-01 1:36 ` pkubaj at anongoth dot pl [this message] 2020-09-16 19:20 ` cvs-commit at gcc dot gnu.org 2021-03-24 20:03 ` iains at gcc dot gnu.org 2021-03-24 20:55 ` pkubaj at anongoth dot pl 2021-03-24 21:12 ` iains at gcc dot gnu.org 2021-04-10 17:03 ` pkubaj at anongoth dot pl 2024-03-17 4:18 ` iains at gcc dot gnu.org 2024-03-17 10:45 ` pkubaj at anongoth dot pl 2024-03-17 19:00 ` 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-89494-4-MoLazAbVlB@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: linkBe 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).