public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bsdfan3 at users dot sourceforge dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/19171] New: <sys/reent.h> causes segfault ICE in GCC 4 Date: Mon, 27 Dec 2004 21:30:00 -0000 [thread overview] Message-ID: <20041227213015.19171.bsdfan3@users.sourceforge.net> (raw) Files that include <sys/reent.h> on i686-pc-cygwin can cause GCC 4 (10-26-04) to bomb out due to a segfault in the compiler itself. I don't have a backtrace (I don't know how to get one if the ICE occurs during the bootstrap process itself, which it does). -- Summary: <sys/reent.h> causes segfault ICE in GCC 4 Product: gcc Version: 4.0.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: bsdfan3 at users dot sourceforge dot net CC: gcc-bugs at gcc dot gnu dot org GCC build triplet: i686-pc-cygwin GCC host triplet: i686-pc-cygwin GCC target triplet: i686-pc-cygwin http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19171
next reply other threads:[~2004-12-27 21:30 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-12-27 21:30 bsdfan3 at users dot sourceforge dot net [this message] 2004-12-27 21:32 ` [Bug c/19171] " bsdfan3 at users dot sourceforge dot net 2004-12-27 22:08 ` pinskia at gcc dot gnu dot org 2004-12-28 1:19 ` [Bug middle-end/19171] " bsdfan3 at users dot sourceforge dot net 2004-12-28 1:20 ` pinskia at gcc dot gnu dot org 2004-12-28 1:23 ` bsdfan3 at users dot sourceforge dot net 2004-12-28 1:28 ` pinskia at gcc dot gnu dot org 2004-12-28 1:29 ` pinskia at gcc dot gnu dot org 2004-12-28 1:29 ` pinskia at gcc dot gnu dot org 2004-12-28 1:31 ` bsdfan3 at users dot sourceforge dot net 2004-12-28 1:59 ` bsdfan3 at users dot sourceforge dot net 2004-12-28 5:02 ` pinskia at gcc dot gnu dot org 2004-12-28 14:27 ` bsdfan3 at users dot sourceforge dot net 2004-12-30 1:25 ` bsdfan3 at users dot sourceforge dot net
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=20041227213015.19171.bsdfan3@users.sourceforge.net \ --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: linkBe 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).