Thanks for your detailed answers!
Mr. Than, can you also shed some light on the calling conventions (CC)?
I got the impression CC might be a serious obstacle for some projects using
LLVM as backend (Mono, llilc).
What is situation with go-CC in gollvm? Is it easy to use standart llvm
solutions for (non c/c++) CC?
Could inline asm features be a simple solutions?
void foo( void)
{
asm( /*read formal or extended parameters*/);
...;
asm( /*write formal or extended parameters*/);
return;
}
Or can some new llvm-intrinsics (with MachineCode stage expanding) or
something also to simplify a CC-task?
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to golang-nuts+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/golang-nuts/12d30be1-3e8c-4ca8-8fa7-83952a53104e%40googlegroups.com.
