public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/105561] Nondeterministic ICE on creation of bits/stdc++.h.gch/O2g.gch and bits/extc++.h.gch/O2g.gch
Date: Wed, 11 May 2022 11:05:17 +0000 [thread overview]
Message-ID: <bug-105561-4-Bg52dlV0Md@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105561-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105561
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Build| |i386-unknown-netbsdelf9.2
Target| |i386-unknown-netbsdelf9.2
Host| |i386-unknown-netbsdelf9.2
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
I wonder if you can get a backtrace from gdb for the crash? When you add -v
to the failing command you should see cc1plus being invoked, trace on that
command.
Does NetBSD have address space randomization? That might influence whether the
bug reproduces or not.
next prev parent reply other threads:[~2022-05-11 11:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-11 10:47 [Bug bootstrap/105561] New: " swilde@sha-bang.de
2022-05-11 11:05 ` rguenth at gcc dot gnu.org [this message]
2022-05-11 12:38 ` [Bug bootstrap/105561] " swilde@sha-bang.de
2022-05-11 13:02 ` swilde@sha-bang.de
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-105561-4-Bg52dlV0Md@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).