Re: Compiler support for a faster interrupt response

mav@sleepy.local.org (Maurizio Vitale)
Fri, 29 Sep 1995 14:24:29 GMT

          From comp.compilers

Related articles
Re: Compiler support for a faster interrupt response ah739@cleveland.Freenet.Edu (1995-09-29)
Re: Compiler support for a faster interrupt response whalley@sed.cs.fsu.edu (David Whalley) (1995-09-29)
Re: Compiler support for a faster interrupt response mav@sleepy.local.org (1995-09-29)
Re: Compiler support for a faster interrupt response sethml@sloth.ugcs.caltech.edu (1995-10-03)
Re: Compiler support for a faster interrupt response gary@Intrepid.COM (1995-10-06)
Re: Compiler support for a faster interrupt response hdlambri@cs.arizona.edu (Henry Dan Lambright) (1995-10-26)
| List of all articles for this month |

Newsgroups: comp.compilers
From: mav@sleepy.local.org (Maurizio Vitale)
Keywords: optimize, architecture
Organization: Godcorp
References: 95-09-154
Date: Fri, 29 Sep 1995 14:24:29 GMT

yoon ji hoon_4S <yjh@news.kreonet.re.kr> writes:


> Whenever interrupt occurs, it is basically true that
> all global registers should be saved in the interrupt
> prolog and restored in the epilog.


Sounds basically false to me:


first of all only registers which are actually _used_ in the
                interrupt handler must be saved. Second thing interrupt
                handlers often check a few things (like a character being
                available somewhere or other change of state in devices) and
                this can be often done with very few registers, so you might
                be able to push the saving/restoring of registers down paths
                that are rarely executed.
--


Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.