search for: kosada

...runFunction, file MCJIT.cpp, line 180." echo -e '#include <iostream>\nextern "C" {void *__dso_handle = NULL;} int main(){ std::cout << "hello" << std::endl; }' | clang -cc1 -emit-llvm-bc -x c++ | lli -use-mcjit --- Jaymie Strecker jstrecker at kosada.com

...9;m having to convert the argument value (the original struct type) to match the parameter type (which could be any of the above variations). Is there a unified way to work with all these variations? Or is there a way to avoid generating them in the first place? --- Jaymie Strecker jstrecker at kosada.com

Le 14 déc. 2012 à 17:08, Jaymie Strecker <jstrecker at kosada.com> a écrit : > Duncan, thanks for your reply. > >> Probably the types are not defined precisely the same in each module (maybe you >> could send the exact definitions in each module to the mailing list?), > > > In the module loaded in Step 1 (otherModule): &gt...

Duncan, thanks for your reply. > Probably the types are not defined precisely the same in each module (maybe you > could send the exact definitions in each module to the mailing list?), In the module loaded in Step 1 (otherModule): %struct.dispatch_group_s = type opaque %union.dispatch_object_t = type { %struct.dispatch_object_s* } %struct.dispatch_object_s = type opaque In the

...;. Except that I would have expected the Linker to recognize that the `dispatch_object_t` type in the loaded module and the generated code are the same. Am I doing something wrong, or is this a bug in LLVM? (I have LLVM 3.1, Mac OS X 10.6.) Thanks for your time. --- Jaymie Strecker jstrecker at kosada.com -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20121213/2f387c8f/attachment.html>