Path: utzoo!attcan!uunet!tut.cis.ohio-state.edu!ucbvax!agate!brahms.berkeley.edu!koonce
From: koonce@brahms.berkeley.edu (tim koonce)
Newsgroups: comp.os.os9
Subject: Re: Buggy Microware 6809 C Compiler
Keywords: c bugs microware compiler coco unix
Message-ID: <1990Jul9.180504.26844@agate.berkeley.edu>
Date: 9 Jul 90 18:05:04 GMT
References: <3583@umbc3.UMBC.EDU>
Sender: usenet@agate.berkeley.edu (USENET Administrator;;;;ZU44)
Reply-To: koonce@brahms.berkeley.edu.UUCP (tim koonce)
Followup-To: comp.os.os9
Organization: University of California, Berkeley
Lines: 27

In article <3583@umbc3.UMBC.EDU> paulr@umbc5.umbc.edu (Paul Riddle) writes:
>So, my question is:  does anyone have a documented list of nasty little bugs
>like this?  I haven't tried the standard Microware C library with the original
>code, but I kind of doubt that the Krieder Library is at fault here.  Of
>course, I could be wrong.
>

I've seen a couple of bug lists around.  The two worst ones I know are:

- Goto handling is pretty messed up.  Greg Law on Delphi studied this,
  and concluded that it's the result of a well-intentioned attempt to
  neatly handle the stack frame.  Turns out that using Goto's will
  cause the stack to walk.

- Multi-dimensional arrays are interpreted in a different order within
  functions than without.  i.e. don't use global multi-dimensional
  arrays.

- Eddie Kuns ran across a problem where for statements with a null
  increment statement were handled incorrectly.  Don't remember the
  details.

Not too bad for a 10-year old compiler running on an 8-bit processor
that I managed to pick up on sale for only $50, but annoying
nonetheless.

                              - Tim Koonce