home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.lang.c++:16057 comp.std.c++:1531
- Newsgroups: comp.lang.c++,comp.std.c++
- Path: sparky!uunet!ukma!netsys!decwrl!concert!sas!mozart.unx.sas.com!sasghm
- From: sasghm@theseus.unx.sas.com (Gary Merrill)
- Subject: Re: something nasty report
- Originator: sasghm@theseus.unx.sas.com
- Sender: news@unx.sas.com (Noter of Newsworthy Events)
- Message-ID: <BxIp1L.M37@unx.sas.com>
- Date: Tue, 10 Nov 1992 20:32:08 GMT
- References: <1992Nov10.192157.20810@BofA.com>
- Nntp-Posting-Host: theseus.unx.sas.com
- Organization: SAS Institute Inc.
- Lines: 23
-
-
- In article <1992Nov10.192157.20810@BofA.com>, dan@BofA.COM (Dan Brockman) writes:
- |> re:
- |> During a C++ compilation ...
- |> "Leg1.c", line 87: internal <<AT&T C++ Translator
- |> 2.1.03 08/31/90>> error: bus error (or something
- |> nasty like that)
- |> Compilation failed
-
- ...
-
- |> The error message may be symptomatic of a broad range
- |> of problems, for many tentative diagnoses were
- |> nominated. I found one problem. It occurs in that
- |> part of the C++ translator called "cfront". It is
- |> not clear to me whether cfront contains a bug.
-
- When a compiler dies with an internal error, causes an access
- violation, etc. it is *always* a bug.
- --
- Gary H. Merrill [Principal Systems Developer, C Compiler Development]
- SAS Institute Inc. / SAS Campus Dr. / Cary, NC 27513 / (919) 677-8000
- sasghm@theseus.unx.sas.com ... !mcnc!sas!sasghm
-