Xref: utzoo comp.sys.amiga.tech:8963 comp.sys.amiga:46205
Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!tut.cis.ohio-state.edu!pt.cs.cmu.edu!andrew.cmu.edu!bader+
From: bader+@andrew.cmu.edu (Miles Bader)
Newsgroups: comp.sys.amiga.tech,comp.sys.amiga
Subject: Re: __chip keyword is evil (was Re: Lattice bugs still?)
Message-ID: <8ZY5kIe00Uka80f8BL@andrew.cmu.edu>
Date: 21 Dec 89 04:29:08 GMT
References: <10415@etana.tut.fi> <9532@microsoft.UUCP> <411@enuxha.eas.asu.edu> <3756@quanta.eng.ohio-state.edu>,
	<10011@microsoft.UUCP>
Organization: Information Technology Center, Carnegie Mellon, Pittsburgh, PA
Lines: 15
In-Reply-To: <10011@microsoft.UUCP>

I was under the impression that #pragma directives as defined by ANSI were
NOT allowed to be used for anything that changed the meaning of the program.
I.e., it has to work the same if the compiler ignores all #pragmas (if
perhaps less quickly, etc).

None of the lattice extensions (__chip, __asm, etc), seem to fit that
definition, so it would seem that you couldn't legally use #pragma to
implement them.  If something needs to be in chip memory, you can't just not
put it there!

Note that the lattice system call hack #pragmas ARE legal, since if you
ignore them, the program just ends up using the library stub instead--
slower, but with the same result.

-Miles