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: Sat, 10 Apr 2021 17:03:20 +0000 [thread overview]
Message-ID: <bug-89494-4-bUwWy5Yj5E@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
--- Comment #30 from Piotr Kubaj <pkubaj at anongoth dot pl> ---
With default flags:
during RTL pass: cprop_hardreg
In file included from
/wrkdirs/usr/ports/lang/gcc10-devel/work/gcc-10-20210327/libgcc/unwind-c.c:32:
/wrkdirs/usr/ports/lang/gcc10-devel/work/gcc-10-20210327/libgcc/unwind-pe.h: In
function 'base_of_encoded_value':
/wrkdirs/usr/ports/lang/gcc10-devel/work/gcc-10-20210327/libgcc/unwind-pe.h:121:1:
internal compiler error: Segmentation fault
With my hack that allows gcc9 to build:
during RTL pass: reload
In file included from
/wrkdirs/usr/ports/lang/gcc10-devel/work/gcc-10-20210327/libiberty/regex.c:639:
/wrkdirs/usr/ports/lang/gcc10-devel/work/gcc-10-20210327/libiberty/regex.c: In
function 'byte_regex_compile':
/wrkdirs/usr/ports/lang/gcc10-devel/work/gcc-10-20210327/libiberty/regex.c:4223:1:
internal compiler error: Segmentation fault
4223 | } /* regex_compile */
The hack is:
CFLAGS_FOR_TARGET="-O0" CXXFLAGS_FOR_TARGET="-O0" BOOT_CFLAGS="-O0"
And the patch:
--- libgcc/config/rs6000/t-crtstuff.orig 2020-04-07 15:17:50 UTC
+++ libgcc/config/rs6000/t-crtstuff
@@ -3,4 +3,4 @@
# Do not build crtend.o with -Os as that can result in references to
# out-of-line register save/restore functions, which may be unresolved
# as crtend.o is linked after libgcc.a. See PR45053.
-CRTSTUFF_T_CFLAGS = -msdata=none -O2 -fno-asynchronous-unwind-tables
+CRTSTUFF_T_CFLAGS = -msdata=none -O0 -fno-asynchronous-unwind-tables
next prev parent reply other threads:[~2021-04-10 17:03 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
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 [this message]
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-bUwWy5Yj5E@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).