|Re: Compiler support for a faster interrupt response ah739@cleveland.Freenet.Edu (1995-09-29)|
|Re: Compiler support for a faster interrupt response firstname.lastname@example.org (David Whalley) (1995-09-29)|
|Re: Compiler support for a faster interrupt response email@example.com (1995-09-29)|
|Re: Compiler support for a faster interrupt response firstname.lastname@example.org (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 email@example.com (Henry Dan Lambright) (1995-10-26)|
|From:||firstname.lastname@example.org (Seth M. LaForge)|
|Organization:||California Institute of Technology, Pasadena, CA|
|Date:||Tue, 3 Oct 1995 17:56:03 GMT|
yoon ji hoon_4S <email@example.com> wrote:
>Whenever interrupt occurs, it is basically true that
>all global registers should be saved in the interrupt
>prolog and restored in the epilog.
Why? On all processors that I've worked with, there is no reason to
save and restore any registers which you don't modify in your
interrupt routine. On the 68K and 6.8K processors you don't even have
to explicitly save and restore registers in interrupt handlers, since
they're saved automatically in the interrupt frame.
>But in the case of 29K processor, nearly 40 ~ 50 registers
>should be saved and restored at each interrupt, which, of course,
>increses the interrupt response time.
>Thus I want to survey various existing techniques for conquering this
>heavy register saving/restoring problem.
>Would you help me?
As I mentioned above, don't use many registers and you don't have to
pay for many registers.
Return to the
Search the comp.compilers archives again.