From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,61906de70bb3bbad X-Google-Attributes: gid103376,public From: Stefan Muehlebach Subject: Re: Interrupt Service Routine in ADA Date: 1998/01/19 Message-ID: <34C32749.919B499D@htl-bw.ch>#1/1 X-Deja-AN: 317301210 Content-Transfer-Encoding: 7bit References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Complaints-To: news@ubnnews.unisource.ch X-Trace: ubnnews.unisource.ch 885204883 27649 (None) 147.86.130.36 Organization: FH Brugg-Windisch Newsgroups: comp.lang.ada Date: 1998-01-19T00:00:00+00:00 List-Id: Steven Coenen wrote: > Does anybody know how to make an interrupt call a tasks entry, i mean when > the interrupt occurs, the entry of the task should be called. > > I tried this but it doesn't work : > entry interrupt > for interrupt use at 16#2C# -- the 16#2C# is the address in the > -- interrupt vector table (IRQ3 interrupt) > > Another questions : is it possible to save the registers (push) in ADA > > Steven, > > EMail : steven.coenen@cs.kuleuven.ac.be Hi Steven It depends which operating system you use. I worked with an Meridian Ada-compiler under DOS and I was able to use an task entry as an interrupt handler - it worked even perfectly. But under other operating systems the 'for ... use ...' statement is interpreted in an other way. Under Unix your entry is not connected to an interrupt but to an Unix-signal.