public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "glaubitz at physik dot fu-berlin.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/95381] [11 Regression]: Bootstrap on m68k fails with ICE: in operator[], at vec.h:867
Date: Fri, 16 Oct 2020 11:50:52 +0000 [thread overview]
Message-ID: <bug-95381-4-H854Hwfgtp@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95381-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95381
--- Comment #8 from John Paul Adrian Glaubitz <glaubitz at physik dot fu-berlin.de> ---
(In reply to Richard Biener from comment #7)
> Still broken?
Unfortunately, yes:
> https://buildd.debian.org/status/fetch.php?pkg=gcc-snapshot&arch=m68k&ver=1%3A20201002-1&stamp=1601807222&raw=0
echo timestamp > stmp-int-hdrs
/<<PKGBUILDDIR>>/build-jit/./gcc/xgcc -B/<<PKGBUILDDIR>>/build-jit/./gcc/ -xc
-nostdinc /dev/null -S -o /dev/null
-fself-test=../../src/gcc/testsuite/selftests
/<<PKGBUILDDIR>>/build-jit/./gcc/xgcc -B/<<PKGBUILDDIR>>/build-jit/./gcc/ -xc++
-nostdinc /dev/null -S -o /dev/null
-fself-test=../../src/gcc/testsuite/selftests
cc1: internal compiler error: in operator[], at vec.h:880
mmap: Bad file descriptor
close: Bad file descriptor
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-snapshot/README.Bugs> for instructions.
cc1plus: internal compiler error: in operator[], at vec.h:880
mmap: Bad file descriptor
close: Bad file descriptor
Please submit a full bug report,
with preprocessed source if appropriate.
I might try a full rebuild in a different environment.
gcc-10 builds fine, FWIW.
next prev parent reply other threads:[~2020-10-16 11:50 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-28 11:35 [Bug target/95381] New: " glaubitz at physik dot fu-berlin.de
2020-05-28 12:35 ` [Bug target/95381] " rguenth at gcc dot gnu.org
2020-05-28 13:03 ` glaubitz at physik dot fu-berlin.de
2020-05-28 21:34 ` glaubitz at physik dot fu-berlin.de
2020-06-09 17:00 ` law at redhat dot com
2020-06-12 10:38 ` glaubitz at physik dot fu-berlin.de
2020-06-16 22:44 ` law at redhat dot com
2020-10-16 11:48 ` rguenth at gcc dot gnu.org
2020-10-16 11:50 ` glaubitz at physik dot fu-berlin.de [this message]
2020-12-29 10:42 ` glaubitz at physik dot fu-berlin.de
2020-12-30 3:25 ` law at redhat dot com
2020-12-30 17:30 ` glaubitz at physik dot fu-berlin.de
2020-12-30 17:38 ` law at redhat dot com
2020-12-30 17:39 ` glaubitz at physik dot fu-berlin.de
2021-01-01 8:24 ` glaubitz at physik dot fu-berlin.de
2021-01-01 9:17 ` doko at debian dot org
2021-01-05 3:46 ` [Bug target/95381] [11 Regression]: Build fails with --disable-bootstrap on m68k " law at redhat dot com
2021-01-14 8:55 ` rguenth at gcc dot gnu.org
2021-04-27 11:38 ` [Bug target/95381] [11/12 " jakub at gcc dot gnu.org
2021-07-28 7:04 ` rguenth at gcc dot gnu.org
2022-04-21 7:48 ` rguenth at gcc dot gnu.org
2022-04-28 15:08 ` [Bug target/95381] [11/12/13 " glaubitz at physik dot fu-berlin.de
2022-04-28 16:04 ` [Bug target/95381] [11 " egallager at gcc dot gnu.org
2023-05-29 10:02 ` jakub 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-95381-4-H854Hwfgtp@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).