public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: Ramon Fernandez <buddyf@webpc.com>
To: egcs-bugs@cygnus.com
Subject: Bug Report: Internal Compiler Error
Date: Sat, 22 Aug 1998 01:58:00 -0000	[thread overview]
Message-ID: <Pine.LNX.3.96.980822045535.13247A-100000@hera.webpc.com> (raw)

Got this error when compiling mindseye

nurbsS.cc: In method `int PlNurbsSurface::writePOVRAY(const char *, const
class Color & = Color(250, 250, 250), const class Point3D & =
Point3D(0x000000000000000000000000, 0x00000000000000000080ff3f,
0x000000000000000000000000), const class Point3D & =
Point3D(0x000000000000000000000000, 0x000000000000000000000000,
0x00000000000000000080ff3f), int = 1, double = 0x000000d8a3703d0ad7a3f83f,
int = 8, int = 8) const':
nurbsS.cc:3191: Internal compiler error.
nurbsS.cc:3191: Please submit a full bug report to `egcs-bugs@cygnus.com'.


I am a RedHat 5.1 Linux system running egcs version egcs-1.0.2-8


If ya need any more info just give me a message..




             reply	other threads:[~1998-08-22  1:58 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-08-22  1:58 Ramon Fernandez [this message]
1998-08-22  8:54 ` Martin von Loewis
  -- strict thread matches above, loose matches on Subject: below --
2006-11-03 15:05 BUG report : Internal compiler error R.J.Sivakumar
2001-06-13 19:05 bug report: " Rob Kaper
2000-09-14  1:16 BUG REPORT: Internal Compiler error Thomas Hendel
     [not found] <Pine.HPX.4.21.0004272125500.1168-101000@verdande.diku.dk>
2000-04-27 13:33 ` bug report: Internal compiler error Martin v. Loewis
1999-10-31 23:03 BUG REPORT: internal " Steve Madsen
1999-10-08  4:23 ` Gerald Pfeifer
1999-06-17 11:09 Bug Report: Internal Compiler Error Bill Wendling
1999-06-30 23:07 ` Martin v. Loewis
1999-05-31 21:06 Bug report: internal compiler error Sascha Schumann
1998-07-10  5:31 C. van Reeuwijk
1998-07-11  7:27 ` Martin von Loewis

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=Pine.LNX.3.96.980822045535.13247A-100000@hera.webpc.com \
    --to=buddyf@webpc.com \
    --cc=egcs-bugs@cygnus.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: 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).