public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/96378] segfault during bootstrap with --disable-checking
Date: Sat, 19 Dec 2020 08:02:30 +0000 [thread overview]
Message-ID: <bug-96378-4-5V5RgVWOFk@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96378-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96378
Eric Botcazou <ebotcazou at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |NEW
Summary|ICE: Solaris/SPARCv9 |segfault during bootstrap
|bootstrap stage2 segfault |with --disable-checking
|compiling |
|stdc++.h.gch/O2ggnu++0x.gch |
--- Comment #6 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
> Thanks! configuring with --enable-checking=release allowed it to compile.
You're welcome. We strongly discourage to configure with --disable-checking
because the compiler will generally not stop in cases where it is confused.
The build should not segfault with it though, so keeping the PR open.
prev parent reply other threads:[~2020-12-19 8:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-29 16:23 [Bug bootstrap/96378] New: ICE: Solaris/SPARCv9 bootstrap stage2 segfault compiling stdc++.h.gch/O2ggnu++0x.gch nicholas.h.briggs at gmail dot com
2020-09-18 8:50 ` [Bug bootstrap/96378] " ebotcazou at gcc dot gnu.org
2020-09-18 16:05 ` nicholas.h.briggs at gmail dot com
2020-12-18 3:07 ` nicholas.h.briggs at gmail dot com
2020-12-18 8:11 ` ebotcazou at gcc dot gnu.org
2020-12-19 2:30 ` nicholas.h.briggs at gmail dot com
2020-12-19 8:02 ` ebotcazou at gcc dot gnu.org [this message]
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-96378-4-5V5RgVWOFk@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).