search for: testclass1

Hi All, I have a question on the type definitions that Clang generates when compiling for x86-64. Here is the C++ code that I compile: class TestClass1 { int X; public: virtual int Foo() { return 1; } }; class TestClass2 : public TestClass1 { int X; public:...

...interpreter // This method register the function directly to LLVM //llvm::sys::DynamicLibrary::AddSymbol(mangled_name, func); } std::string getPrintText() { printf("\nRunning getPrintText()...\n"); return std::string("Hello world from getPrintText()!"); } class TestClass1 { public: static void test1() { printf("\nHello World from TestClass1::test1()!\n"); } void test2(std::string s) { printf("\nHello World from TestClass1::test2()! : %s\n",+s.data()); //ConsoleM.newMsg(S+"Hello World from TestClass...

Hi Skykill, > Hello everyone, i’m using LLVM (updated to 3.1 after seeing that bug, but it’s > the same with 3.0) for running a bitcode on a C++ program, and Clang for > compiling it. My code work perfectly, as expected on x64, but crash on x86. I’m > on Windows 7 x64 and LLVM + Clang was compiled using Visual Studio 2010 (tested > in both Release and Debug build). Project was make

...>() Ligne 478 + 0xb octets C++ LLVM_Test_Console.exe!std::basic_string<char,std::char_traits<char>,std::allocator<char> >::~basic_string<char,std::char_traits<char>,std::allocator<char> >() Ligne 754 + 0xf octets C++ LLVM_Test_Console.exe!TestClass1::test2(std::basic_string<char,std::char_traits<char>,std::allocator<char> > s) Ligne 172 + 0xf octets C++ 01180091() LLVM_Test_Console.exe!llvm::JIT::runFunction(llvm::Function * F, const std::vector<llvm::GenericValue,std::allocator<llvm::GenericValue> &...