public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "doko at debian dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/97314] New: bootstrap failure on i686-linux-gnu with --enable-checking=yes,extra,rtl
Date: Wed, 07 Oct 2020 08:06:28 +0000 [thread overview]
Message-ID: <bug-97314-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97314
Bug ID: 97314
Summary: bootstrap failure on i686-linux-gnu with
--enable-checking=yes,extra,rtl
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: bootstrap
Assignee: unassigned at gcc dot gnu.org
Reporter: doko at debian dot org
Target Milestone: ---
seen with the gcc-10 branch 20201003, while originally building that for
another architecture. The build succeeds on another 32bit arch
(arm-linux-gnueabihf) and on 64bit archs, but fails on i686-linux-gnu.
The build is also configured with --enable-default-pie and other hardening
options turned on by default, built with make -j2.
virtual memory exhausted: Operation not permitted
make[5]: *** [Makefile:1117: insn-extract.o] Error 1
make[5]: *** Waiting for unfinished jobs....
rm gcc.pod gfortran.pod cpp.pod gccbrig.pod gccgo.pod gdc.pod
make[5]: Leaving directory '/<<PKGBUILDDIR>>/build/gcc'
make[4]: *** [Makefile:4878: all-stage3-gcc] Error 2
make[4]: Leaving directory '/<<PKGBUILDDIR>>/build'
make[3]: *** [Makefile:27347: stage3-bubble] Error 2
make[3]: Leaving directory '/<<PKGBUILDDIR>>/build'
make[2]: *** [Makefile:27411: bootstrap] Error 2
make[2]: Leaving directory '/<<PKGBUILDDIR>>/build'
next reply other threads:[~2020-10-07 8:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-07 8:06 doko at debian dot org [this message]
2020-10-07 8:46 ` [Bug bootstrap/97314] " rguenth at gcc dot gnu.org
2020-10-07 9:00 ` jakub at gcc dot gnu.org
2020-11-17 15:14 ` rsandifo at gcc dot gnu.org
2020-12-07 8:35 ` doko at debian dot 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-97314-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).