public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: rth@gcc.gnu.org To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, rth@gcc.gnu.org, stefaandr@hotmail.com Subject: Re: target/5851: tmp-dum.c:2: Internal error: Segmentation fault Date: Sun, 31 Mar 2002 15:44:00 -0000 [thread overview] Message-ID: <20020331234359.10783.qmail@sources.redhat.com> (raw) Synopsis: tmp-dum.c:2: Internal error: Segmentation fault State-Changed-From-To: feedback->closed State-Changed-By: rth State-Changed-When: Sun Mar 31 15:43:59 2002 State-Changed-Why: From: Stefaan De Roeck <stefaandr@hotmail.com> Date: Mon, 1 Apr 2002 00:34:19 +0200 (CEST) The original problem was indeed a crash in the compiler, as I reported. This probleem seems to be solved in the prerelease. My next stop will be the binutils-bugreport mailinglist then. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5851
next reply other threads:[~2002-03-31 23:44 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-03-31 15:44 rth [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-03-30 16:36 Richard Henderson 2002-03-30 16:16 Stefaan De Roeck 2002-03-29 17:21 rth
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=20020331234359.10783.qmail@sources.redhat.com \ --to=rth@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=stefaandr@hotmail.com \ /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).