Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!utfyzx!oscvax!rico
From: rico@oscvax.UUCP
Newsgroups: comp.sys.amiga
Subject: Re: Aztec C bug
Message-ID: <534@oscvax.UUCP>
Date: Sat, 21-Nov-87 20:06:56 EST
Article-I.D.: oscvax.534
Posted: Sat Nov 21 20:06:56 1987
Date-Received: Wed, 25-Nov-87 02:43:09 EST
References: <532@oscvax.UUCP> <4993@zen.berkeley.edu>
Reply-To: rico@oscvax.UUCP (Rico Mariani)
Distribution: na
Organization: Ontario Science Centre, Toronto
Lines: 34
Summary: 

In article <4993@zen.berkeley.edu> waterman@cory.Berkeley.EDU.UUCP (T.S. Alan Waterman) writes:
>
> rico@oscvax.UUCP (Rico Mariani) writes:
>>
>> main()
>> {
>>	struct foo { int x; } bar;
>>
>>	if (bar) ;
>> }
>>
>> compiles to:
>
>    No. The only compiler bug here is that it didn't give you a big
>flaming error message (multiple lines, ^'s and all, Mike :^).

I know... that's the point.  I included the assembler output because
I thought it might help someone find the problem...

>    This is a program bug, not a compiler bug. 

No matter what I type at the compiler it should never produce invalid
assembler code.  Although if it's going to blow it, I'd much rather
that it produce code the assembler barfs on that quietly produce
code that's wrong.

	-Rico
-- 
		...{watmath|allegra|decvax|ihnp4|linus}!utzoo!oscvax!rico
		or oscvax!rico@gpu.toronto.EDU   if you're lucky

[NSA food: terrorist, cryptography, DES, drugs, CIA, secret, decode]
[CSIS food: supermailbox, tuna, fiberglass coffins, Mirabel, microfiche]
[Cat food: Nine Lives, Cat Chow, Meow Mix, Crave]