[fpc-devel] Interrupt vector table generation
Jeppe Johansen
jepjoh2 at es.aau.dk
Mon Mar 21 23:38:13 CET 2011
Den 13-03-2011 16:37, Florian Klämpfl skrev:
> Am 13.03.2011 16:34, schrieb Jonas Maebe:
>> On 13 Mar 2011, at 16:31, Florian Klämpfl wrote:
>>
>>> Am 06.03.2011 22:46, schrieb Jeppe Johansen:
>>>> Further, a future benefit of using the interrupt keyword could be
>>>> generation of procedure exit code. Some platforms need a special "return
>>>> from exception/interrupt" instructions at the end of interrupt handlers
>>>>
>>>> I've made an implementation of this here:
>>>> http://j-software.dk/interrupttable.patch.txt
>>> I think when searching for interrupt handlers, also the procdefs should
>>> be processed.
>> It would be nice if it could be done with less ifdefs all over the place though.
> Yes, I planned to remove them and depend on systems_interrupt_table as
> much as possible.
An update here: http://j-software.dk/interrupttable3.patch.txt
I removed a good deal of the ifdefs
Added a new calling convention pocall_interrupt - which is only set if
there's an interrupt vector specified
Fixed the procdef searching
Any opinions? :)
More information about the fpc-devel
mailing list