Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site brl-tgr.ARPA
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!genrad!wjh12!harvard!seismo!brl-tgr!gwyn
From: gwyn@brl-tgr.ARPA (Doug Gwyn )
Newsgroups: net.lang.c
Subject: Re: a use for &LABEL
Message-ID: <4918@brl-tgr.ARPA>
Date: Thu, 27-Sep-84 17:09:20 EDT
Article-I.D.: brl-tgr.4918
Posted: Thu Sep 27 17:09:20 1984
Date-Received: Sat, 29-Sep-84 09:45:01 EDT
References: <525@nmtvax.UUCP>
Organization: Ballistics Research Lab
Lines: 8

It is unlikely that you will like the results of an interrupt jumping
into the middle of your C code.  For one thing, this bypasses the stack
frame set-up so your auto variables will be stolen from whatever stack
frame happens to be set at interrupt time.  The preferred way to handle
interrupts with C functions is to write a little assembly-language
interface that saves all registers etc. and calls the C function with
valid arguments, then restores the machine state before RTI.  Your Manx
C system includes an assembler that can be used for this.