search for: 20ffi

Hi, I want to declare a function that matches C ABI. Do I need to transform declarations like void @f(%struct.A %a) into void @f(%struct.A* byval %a) myself or LLVM can do it for me? Is this what "ccc" calling convention means? - Paweł -------------- next part -------------- An HTML attachment was scrubbed... URL:

...omeone constructing the proper classes to > pass to clang to have it emit the C ABI calls from their non-C language, > although I'm not sure where I saw that. There was an interesting talk a couple years ago about how Swift embeds clang: http://llvm.org/devmtg/2014-10/Slides/Skip%20the%20FFI.pdf Now that it's open-source the code might be of interest. -Ahmed > _______________________________________________ > LLVM Developers mailing list > llvm-dev at lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev >

Hi everyone, I took a look at the IR modules clang generates, and how clang translates functions in C++ namespace and classes. I've understood how it works for namespace but is there a file or a documentation that explains how Clang translates namespaces and classes in the IR modules? If this becomes a convention all the front-end languages will be able to create functions available to other

On Mon, Mar 28, 2016 at 5:14 PM, Michael Nicolella via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Thanks for the explanation. It's good to hear the situation isn't felt to > be ideal. > > The details here are going to be sensitive to the OS + target that I'm > compiling for, right? So the effort here will be to understand and get > right the calling

Thanks for the explanation. It's good to hear the situation isn't felt to be ideal. The details here are going to be sensitive to the OS + target that I'm compiling for, right? So the effort here will be to understand and get right the calling convention details for each supported target, yes? Is there any current plan to change the way this works, or is it more of a dreamy cleanup

Hello, In my LLVM frontend (CLR/MSIL), I am currently using first-class aggregates to represent loaded value types on the "CLR stack". However, I noticed that when calling external method taking those aggregate by value, they were not passed as I expected: %COLORREF = type { i8, i8, i8, i8 } declare i32 @SetLayeredWindowAttributes(i8*, %COLORREF, i8, i32) I call this function with