Return to the
comp.compilers page.
Search the
comp.compilers archives again.
| 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) |
| Newsgroups: | comp.compilers |
| From: | ah739@cleveland.Freenet.Edu (Leslie J. Somos) |
| Keywords: | optimize, architecture |
| Organization: | Case Western Reserve University, Cleveland, OH (USA) |
| References: | 95-09-154 |
| Date: | Fri, 29 Sep 1995 08:02:53 GMT |
In a previous article, yjh@news.kreonet.re.kr (yoon ji hoon_4S) says:
>Whenever interrupt occurs, it is basically true that
>all global registers should be saved in the interrupt
>prolog and restored in the epilog.
[...]
Not necessarily. As long as you control all code running,
you could enforce the opposite convention, that the
interrupt routine only save those registers that it plans
on using, and then restore just those upon exit.
Of course, it's much safer to do a blanket save and restore
as you describe.
--
Return to the
comp.compilers page.
Search the
comp.compilers archives again.