search for: xyzisellow

...t; (int64_t would in almost every case map to i64, and this straight > return should be fine, particularly if it comes from C++). So are you > using a custom target and does it have any quirks that might be > relevant? The key functions to look at would be LowerCall and > LowerReturn in XYZISelLowering.cpp. > > Cheers. > > Tim. > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20170712/3a92a864/attachment-0001.html>

Hello, everyone, I encounter a strange problem about llvm type i64 and C++ type int64_t. I instrumented a program to call the function 'myFunction' in the C++ shared library. 'myFunction' is something like this: int64_t myFunction() { int64_t retValue; ... std::cout << "retValue: " << retValue << "\n"; return retValue; }

...uage's front-end. > 3.) Can I implement my own custom calling convention? Like my own > "__planschiCall" or something? Yes. The easiest way would be to use a simple numbered calling convention "cc N" in the LLVM IR. Then you just have to add support to lib/Target/XYZ/XYZISelLowering.cpp and the corresponding calling convention .td file (the name varies a bit). ISelLowering usually just involves a switch based on the call or definition that selects the right implementation from the .td file. Grep for CCAssignFnForCall to see the kind of thing you'll be changing. Clang...

Hello everyone, I have some questions about the possibilities with the LLVM but I'm not sure where to gather the information. 1.) Can I teach the LLVM new platform depended intrinsics? Like I provide assembly code and want to create a custom intrinsic for it. 2.) Does the IR language have some kind of template support? I'm not sure if this even possible - but I thought about having a