delorie.com/archives/browse.cgi | search |
From: | Skye <s_c AT iname DOT com> |
Newsgroups: | comp.os.msdos.djgpp |
Subject: | Re: Real mode ISR's |
Date: | Sun, 13 Apr 1997 21:31:23 -0700 |
Organization: | Uniserve |
Lines: | 16 |
Message-ID: | <3351B31B.6C35@iname.com> |
References: | <5iqtre$jt7 AT lion DOT cs DOT latrobe DOT edu DOT au> |
Reply-To: | s_c AT iname DOT com |
NNTP-Posting-Host: | van0223.tvs.net |
Mime-Version: | 1.0 |
To: | djgpp AT delorie DOT com |
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
Gregary J Boyles wrote: > > Which are the steps which need to be taken on entering and leaving an ISR? > I can't find any info which will tell me and I am used to using the > Borland key word 'interrupt'. > > When using _go32_dpmi_allocate_dos_memory(...) I was going to enclose the > ISR function and variables it uses inside two dummy functions and do > pointer arithmetic to determine the size of the memory required. Is there > any way of ensuring that gcc won't rearrange the variables or functions? You might want to take a look at Shawn's Allegro code if you have it and see how he manages it. I found it and the FAQ to be very good references for this. -SC
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |