Displaying 4 results from an estimated 4 matches for "__builtin_stm8_far_storen".
2011 Feb 22
1
[LLVMdev] STM8 backend for Clang
...M doesn't support distinguishing between near and far pointers.
> Depending on how much work you want to put in and what exactly you'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...
2011 Feb 21
0
[LLVMdev] STM8 backend for Clang
...d far pointers?
LLVM doesn't support distinguishing between near and far pointers.
Depending on how much work you want to put in and what exactly you'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.
> Anyway, I've put together enough skeleton code to successfully
> compile, but on Mac OS X v10.5 ppc host this is what I get:
>
> $ Debug+Asserts/bin/clang -ccc-host-triple stm8-unknown-elf ../hello.c
> -S -o ../hello.s
> 0 clang 0x0168c4f0...
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
...M doesn't support distinguishing between near and far pointers.
> Depending on how much work you want to put in and what exactly you'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...