Displaying 7 results from an estimated 7 matches for "interrupt_handler".
2009 Jul 21
0
[LLVMdev] LLVM and Interrupt Service Routines.
Hi Sanjiv,
Assuming that that support for Ada in LLVM is complete, I would look
to see if there is something that is done there. Ada provides two
pragmas (Interrupt_Handler & Attach_Handler) which allow you to both
statically and dynamically attach interrupts to procedures.
Alex Karahalios
On Jul 21, 2009, at 8:07 AM, <Sanjiv.Gupta at microchip.com> <Sanjiv.Gupta at microchip.com
> wrote:
> Apparently, there is no explicit support for ISRs in...
2011 Feb 22
1
[LLVMdev] STM8 backend for Clang
...;re
> trying to build, you might be able to get away with just pretending
> all pointers are near and implementing __builtin_stm8_far_loadn() and
> __builtin_stm8_far_storen() intrinsics, though.
The example C code uses far pointers, e.g., to set up interrupt vectors:
typedef void @far (*interrupt_handler_t)(void);
struct interrupt_vector
{
unsigned char interrupt_instruction;
interrupt_handler_t interrupt_handler;
};
So I do need support for 24-bit pointers in the Clang frontend, in
order for the struct to fill four bytes here.
Not sure how intrinsics could help there. I assume that @far...
2009 Jul 21
7
[LLVMdev] LLVM and Interrupt Service Routines.
Hi,
Apparently, there is no explicit support for ISRs in the llvm framework. I could not find a matching attribute that can be used to mark a function as an ISR, which codegen and optimizer can use accordingly. ISRs aren't called explicity from any function, so currently the optimizer deletes them. We are planning to introduce a new "interrupt" attribute (to be modeled similiar to
2009 Jul 22
3
[LLVMdev] LLVM and Interrupt Service Routines.
Hi Alex,
> Assuming that that support for Ada in LLVM is complete, I would look to
> see if there is something that is done there. Ada provides two pragmas
> (Interrupt_Handler & Attach_Handler) which allow you to both statically
> and dynamically attach interrupts to procedures.
the interrupt handler itself is a parameterless procedure that does not
return a value. As such, I guess calling conventions and so forth are
not very relevant for it :) In any case ll...
2011 Feb 21
0
[LLVMdev] STM8 backend for Clang
On Sun, Feb 20, 2011 at 4:23 PM, Andreas Färber <andreas.faerber at web.de> wrote:
> Hi there,
>
> Inspired by the recent FOSDEM keynote, I've tried to write an LLVM
> backend for the STM8 microcontroller platform. The STM8S-Discovery
> evaluation board [1] has been handed out for free or is sold dirt-
> cheap, but there is no Open Source cross-compiler for it. The
>
2011 Feb 21
3
[LLVMdev] STM8 backend for Clang
Hi there,
Inspired by the recent FOSDEM keynote, I've tried to write an LLVM
backend for the STM8 microcontroller platform. The STM8S-Discovery
evaluation board [1] has been handed out for free or is sold dirt-
cheap, but there is no Open Source cross-compiler for it. The
available ST assembler, linker and USB flash programmer are closed-
source Windows binaries. And the compiler
2011 Feb 23
0
[LLVMdev] LLVMdev Digest, Vol 80, Issue 37-Help to unsubscribe
...;re
> trying to build, you might be able to get away with just pretending
> all pointers are near and implementing __builtin_stm8_far_loadn() and
> __builtin_stm8_far_storen() intrinsics, though.
The example C code uses far pointers, e.g., to set up interrupt vectors:
typedef void @far (*interrupt_handler_t)(void);
struct interrupt_vector
{
unsigned char interrupt_instruction;
interrupt_handler_t interrupt_handler;
};
So I do need support for 24-bit pointers in the Clang frontend, in
order for the struct to fill four bytes here.
Not sure how intrinsics could help there. I assume that @far is...