search for: conflict_redo

...;t ideal). Assuming you have full control over your environment, I'd not start by writing a new calling convention. I'd just have: ... %dest = load_from_itable() call i32 %dest(i32 METHOD_ID, rest of the arguments ...) ... and have the conflict resolution stub be: define i32 @conflict_redo(i32 %method_id, arg0, arg1, arg2) { dispatch based on %method_id } with the normal x86 calling conventions. Later, as an *optimization* I'd consider a custom calling convention for the %method_id argument. Not using %rax for %method_id frees it up for use as %dest, for instance, so usin...

Hi everyone, I'm the developer of the Loci programming language ( http://loci-lang.org ), for which the compiler is a front-end for LLVM. I would like to say that LLVM has been extremely useful for the development of the compiler and so thank you everyone for building this amazing system. ---- Virtual Method Calls ---- While most aspects of the language map well onto LLVM IR, it seems