Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!cmcl2!rutgers!ukma!eric
From: eric@ms.uky.edu (Eric Herrin)
Newsgroups: comp.lang.c
Subject: Re: asm statements & the stack
Message-ID: <7426@e.ms.uky.edu>
Date: Wed, 7-Oct-87 13:37:59 EDT
Article-I.D.: e.7426
Posted: Wed Oct  7 13:37:59 1987
Date-Received: Sat, 10-Oct-87 09:57:08 EDT
References: <110@teletron.UUCP>
Reply-To: eric@ms.uky.edu (Eric Herrin)
Organization: U of Kentucky, Mathematical Sciences
Lines: 22


My general philosophy when doing this sort of thing is to use static data
structures instead of the stack.  This at least allows the compiler to 
do any funny business it likes with the stack.

The method of keeping the stack pointer pointing at an unused location is
quite common, as I have used many unix compilers which do this.  I believe
if you are going to the trouble of hacking in assembly code anyway, you
should simply look at what is being generated before running the routines.
Then you could, in your case, use the unused location yourself and then
decrement the stack pointer to keep the compiled code happy.


				eric



-- 
|    Eric Herrin II				     	cbosgd!ukma!eric      |
|    "'tis better to be silent                         	eric@UKMA.BITNET      |
|     and be THOUGHT a fool, than to open              	eric@ms.uky.csnet     |
|     one's mouth and remove all doubt."                eric@ms.uky.edu       |