delorie.com/archives/browse.cgi | search |
From: | boylesgj AT lion DOT cs DOT latrobe DOT edu DOT au (Gregary J Boyles) |
Newsgroups: | comp.os.msdos.djgpp |
Subject: | Real mode ISR's |
Date: | 13 Apr 1997 15:24:30 GMT |
Organization: | Comp.Sci & Comp.Eng, La Trobe Uni, Australia |
Lines: | 9 |
Distribution: | world |
Message-ID: | <5iqtre$jt7@lion.cs.latrobe.edu.au> |
NNTP-Posting-Host: | lion.cs.latrobe.edu.au |
To: | djgpp AT delorie DOT com |
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
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?
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |