Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!husc6!think!ames!lll-winken!uunet!mcrware!kim
From: kim@mcrware.UUCP (Kim Kempf)
Newsgroups: comp.os.os9
Subject: Re: C compiler 3.0 BUG with inline assembly!
Keywords: #asm, #endasm, crackerjack_compiler, unix-weenie, figure one
Message-ID: <1003@mcrware.UUCP>
Date: 6 Apr 89 14:44:31 GMT
References: <1248@mmm.UUCP>
Reply-To: kim@mcrware.UUCP (Kim Kempf)
Followup-To: comp.os.os9
Distribution: usa
Organization: Microware Systems Corp., Des Moines, Iowa
Lines: 24

In article <1248@mmm.UUCP> manning@mmm.UUCP (Arthur T. Manning) writes:
>In the following code, the compiler concatenates the two SEPERATE sections
>of assembly together as though they were all inside the if statement's
>scope.  In the second case (with only a semicolon added) the compiler does
>what it is expected to do.  Apparently "}" is not enough for the compiler
>to know that the if{} has ended and to put the rest of the assembly code
>outside the scope.
>
>Would you believe we found this bug in an interrupt service routine?
>
>We would never have found it without our VMETRO vme bus debugger.
>Arthur T. Manning                                Phone: 612-733-4401
>3M Center  518-1                                 FAX:   612-736-3122
>St. Paul  MN  55144-1000   U.S.A.                Email: manning@mmm.uucp

Here we go again....  The comments made here are absolutely untrue. 
This exact situation is described in T.F.M on page 3-3 paragraph 5 on
that page headed "Interfacing to Assembly Language".  The quality OS-9 C
compiler and OS-9 itself is superb as can be attested to by a vast list
of Microware customers.  The list of unsatisfied customers is trivial
and a few of those haunt USENET. 

----------------
Kim Kempf, Microware Systems Corporation	{sun,uunet}!mcrware!kim