Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!usc!apple!sun-barr!decwrl!sgi!davea@quasar.wpd.sgi.com
From: davea@quasar.wpd.sgi.com (David B. Anderson)
Newsgroups: comp.sys.sgi
Subject: Re: Compiler bugs?
Message-ID: <45673@sgi.sgi.com>
Date: 4 Dec 89 17:32:51 GMT
References: <8912040056.aa01435@SMOKE.BRL.MIL>
Sender: davea@quasar.wpd.sgi.com
Reply-To: davea@quasar.UUCP (David B. Anderson)
Organization: Silicon Graphics, Inc., Mountain View, CA
Lines: 27

In article <8912040056.aa01435@SMOKE.BRL.MIL> XBR2D96D@DDATHD21.BITNET (Knobi der Rechnerschrat) writes:
>Hallo,
>
>  I discovered the following two bugs  in the C and f77 compiler of 3.2. I know
>I should report them directly to Calvin Vu, but I've lost his e-mail address.
[stuff deleted about f77]
>  Second, a colleague asked me to test the following c code on our 4D/70-GT.
[stuff deleted]
>else/*comment*/f1();
[stuff deleted]
>The code compiles fine (that's ok), but ld complains about not finding
>_elsef1. That means it just removes the comment without replacing it by a
>white space character as stated by K&R. Thats either a violation of K&Rs'
>definiton of comments, or a violation of the rule that comments may

We use the traditional AT&T Reiser cpp.  That cpp has, as has been
mentioned many times (in other newgroups, not this one), that /* */
behavior.  Since many programs depend on the erroneous behavior cpp
cannot be changed.

In the release after 3.2, we allow optional use of an ANSI cpp (with
the -acpp flag).     acpp does not exibit the behavior mentioned
by Mr. Rechnerschrat.


Regards,
[ David B. Anderson  Silicon Graphics  (415)335-1548  davea@sgi.com ]