public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: satadru@umich.edu To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: other/8531: sparc64 fatal Internal compiler error in `create_reg_dead_note', at haifa-sched.c:4496 when compiling kde3 from OpenBSD ports or mozilla Date: Tue, 10 Dec 2002 11:26:00 -0000 [thread overview] Message-ID: <20021210192602.8096.qmail@sources.redhat.com> (raw) The following reply was made to PR other/8531; it has been noted by GNATS. From: satadru@umich.edu To: ehrhardt@mathematik.uni-ulm.de, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org Cc: Subject: Re: other/8531: sparc64 fatal Internal compiler error in `create_reg_dead_note', at haifa-sched.c:4496 when compiling kde3 from OpenBSD ports or mozilla Date: Tue, 10 Dec 2002 14:24:18 -0500 unfortunately, I'm now on a linux sparc64 system, with a 32bit userland, instead of a OpenBSD sparc64 system with a 64 bit userland, and I no longer have the capability to help with this compiler problem. sat --On Tuesday, December 10, 2002 6:46 PM +0000 ehrhardt@mathematik.uni-ulm.de wrote: > Synopsis: sparc64 fatal Internal compiler error in > `create_reg_dead_note', at haifa-sched.c:4496 when compiling kde3 from > OpenBSD ports or mozilla > > State-Changed-From-To: open->feedback > State-Changed-By: cae > State-Changed-When: Tue Dec 10 10:45:33 2002 > State-Changed-Why: > If this is repeatable please do the following: > Run make until g++ exits with an internal compiler error, then > enter the exact g++ command that make did immediatly before the crash > by hand and add -save-temps. This should produce the same "internal > compiler error" message but will leave a file ending in .ii behind. > Please send this file. That's what we need. > > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gc > c&pr=8531 -- I hope you don't mind if we move our men, so that we have more space to grooove. -Bruce Lee
next reply other threads:[~2002-12-10 19:26 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-12-10 11:26 satadru [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-03-12 18:51 neroden 2002-12-10 12:26 David S. Miller 2002-12-10 10:46 ehrhardt 2002-11-19 12:20 satadru
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=20021210192602.8096.qmail@sources.redhat.com \ --to=satadru@umich.edu \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).