This is the mail archive of the
mailing list for the GCC project.
Re: Interrupts with GCC/EGCS
- To: Michael Schwingen <rincewind at discworld dot dascon dot de>
- Subject: Re: Interrupts with GCC/EGCS
- From: Jeffrey A Law <law at cygnus dot com>
- Date: Fri, 19 Mar 1999 22:59:01 -0700
- cc: crossgcc at cygnus dot com, egcs-patches at cygnus dot com
- Reply-To: law at cygnus dot com
In message <19990318191219.C243@tubul.dascon.de>you write:
> I am not familiar with gcc internals, so I am not sure why it went wrong -
> however, I exactly copied everything from sh3 to m68k, and the effect was
> that when compiling a program with multiple functions, where one had an
> interrupt attribute, the function *before* this one had the interrupt code
> generated (save/restore all regs, and rte), and not the correct function
> (IIRC, this was with -O2).
Possibly because the sh handles prologues/epilogues as RTL, but the
m68k uses FUNCTION_PROLOGUE/FUNCTION_EPILOGUE to emit the prologues
You might want to peek at the H8 port since it uses FUNCTION_PROLOGUE and
FUNCTION_EPILOGUE and supports an interrupt attribute.