search for: executiondriver

...ot;public: virtual void __thiscall llvm::CallTargetFinder::print(class std::basic_ostream<char,struct std::char_traits<char> > &,class llvm::Module const *)const " (?print at CallTargetFinder@llvm@@UBEXAAV?$basic_ostream at DU?$char_traits at D@std@@@std@@PBVModule at 2@@Z) ExecutionDriver.obj : error LNK2019: unresolved external symbol "public: static class llvm::GCC * __cdecl llvm::GCC::create(class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > const &,class std::basic_string<char,struct std::char_traits<char&...

Hi Eli, Thanks for the reply. I tried with -Xlinker="-ldl ". However it does not seem to make a difference. It seems that when bugpoint is run with --run-jit, the linker args are not passed to gcc (from tools/bugpoint/ExecutionDriver.cpp) : if (InterpreterSel == RunLLC || InterpreterSel == RunCBE || InterpreterSel == CBE_bug || InterpreterSel == LLC_Safe) RetVal = AI->ExecuteProgram(BitcodeFile, InputArgv, InputFile, OutputFile, AdditionalLinkerArgs, SharedObjs,...

...* [/local/csaba/LLVM/build-release/Release+Asserts/bin/llc] Error 1 make[2]: Leaving directory `/local/csaba/LLVM/build-release/tools/llc' make[1]: *** [llc/.makeall] Error 2 make[1]: *** Waiting for unfinished jobs.... llvm[2]: Compiling DiffLog.cpp for Release+Asserts build llvm[2]: Compiling ExecutionDriver.cpp for Release+Asserts build llvm[2]: Linking Release+Asserts executable llvm-bcanalyzer (without symbols) llvm[2]: Linking Release+Asserts executable llvm-mc (without symbols) llvm[2]: ======= Finished Linking Release+Asserts Executable llvm-bcanalyzer (without symbols) make[2]: Leaving directory...

..., at 2:55 PM, Prakash Prabhu wrote: > > Hi Eli, > > Thanks for the reply. I tried with -Xlinker="-ldl ". However it does not > seem to make a difference. It seems that when bugpoint is run with > --run-jit, the linker args are not passed to gcc (from > tools/bugpoint/ExecutionDriver.cpp) : > > if (InterpreterSel == RunLLC || InterpreterSel == RunCBE || > InterpreterSel == CBE_bug || InterpreterSel == LLC_Safe) > > RetVal = AI->ExecuteProgram(BitcodeFile, InputArgv, InputFile, > OutputFile, AdditionalLinkerArgs, &gt...

...at 2:55 PM, Prakash Prabhu wrote: > Hi Eli, > > Thanks for the reply. I tried with -Xlinker="-ldl ". However it does > not seem to make a difference. It seems that when bugpoint is run > with --run-jit, the linker args are not passed to gcc (from tools/ > bugpoint/ExecutionDriver.cpp) : > > if (InterpreterSel == RunLLC || InterpreterSel == RunCBE || > InterpreterSel == CBE_bug || InterpreterSel == LLC_Safe) > > RetVal = AI->ExecuteProgram(BitcodeFile, InputArgv, InputFile, > OutputFile, AdditionalLinkerArgs, &...

...rote: > >> Hi Eli, >> >> Thanks for the reply. I tried with -Xlinker="-ldl ". However it >> does not seem to make a difference. It seems that when bugpoint is >> run with --run-jit, the linker args are not passed to gcc (from >> tools/bugpoint/ExecutionDriver.cpp) : >> >> if (InterpreterSel == RunLLC || InterpreterSel == RunCBE || >> InterpreterSel == CBE_bug || InterpreterSel == LLC_Safe) >> >> RetVal = AI->ExecuteProgram(BitcodeFile, InputArgv, InputFile, >> OutputFile, A...

On Tue, Oct 28, 2008 at 12:17 PM, Prakash Prabhu <prakash.prabhu at gmail.com> wrote: > Generating reference output from raw program: <cbe><gcc> > Error running tool: [snip] > /tmp/cc08IpX8.o: In function `SyLoadModule': > bugpoint-test-program.bc.cbe.c:(.text+0x25705): undefined reference to > `dlopen' [snip] This is saying that compilation with CBE is

Hi Scott, > On Tue, May 5, 2009 at 12:26 PM, Duncan Sands <baldrick at free.fr> wrote: > > this is indeed a miscompilation by your system compiler. However so many > > compilers miscompiled this that a workaround was committed to svn. So you > > may want to check out llvm and llvm-gcc from svn. Alternatively, maybe > > the patch applies to llvm 2.5 too.

...lvm-svn2/install/ and then did "make" in the llvm-obj directory. But this build failed: make[2]: Entering directory `/pkg/build/llvm-svn2/llvm-obj/tools/bugpoint' llvm[2]: Compiling BugDriver.cpp for Debug build llvm[2]: Compiling CrashDebugger.cpp for Debug build llvm[2]: Compiling ExecutionDriver.cpp for Debug build llvm[2]: Compiling ExtractFunction.cpp for Debug build llvm[2]: Compiling FindBugs.cpp for Debug build /usr/lib/gcc/x86_64-redhat-linux/4.1.2/../../../../include/c++/4.1.2/bits/ostream.tcc: In member function ‘std::basic_ostream<_CharT, _Traits>& std::basic_ostream<...

On Tue, May 5, 2009 at 12:26 PM, Duncan Sands <baldrick at free.fr> wrote: > this is indeed a miscompilation by your system compiler.  However so many > compilers miscompiled this that a workaround was committed to svn.  So you > may want to check out llvm and llvm-gcc from svn.  Alternatively, maybe > the patch applies to llvm 2.5 too.  I've attached it. I will try the

Hi, I have a program that runs when statically compiled using llc and gcc but crashes with a segmentation fault when run with lli. I am trying to debug it with bugpoint and the initial part of bugpoint seems to be suggesting that I am somehow missing the linking with the libraries having dlsym/dlopen although I am passing it to lli : *$ bugpoint -run-jit

...ng-field-initializers -pedantic -Wno-long-long -Wno-maybe-uninitialized -Wdelete-non-virtual-dtor -Wno-comment -O3 -DNDEBUG -Wl,-search_paths_first -Wl,-headerpad_max_install_names -rdynamic CMakeFiles/bugpoint.dir/BugDriver.cpp.o CMakeFiles/bugpoint.dir/CrashDebugger.cpp.o CMakeFiles/bugpoint.dir/ExecutionDriver.cpp.o CMakeFiles/bugpoint.dir/ExtractFunction.cpp.o CMakeFiles/bugpoint.dir/FindBugs.cpp.o CMakeFiles/bugpoint.dir/Miscompilation.cpp.o CMakeFiles/bugpoint.dir/OptimizerDriver.cpp.o CMakeFiles/bugpoint.dir/ToolRunner.cpp.o CMakeFiles/bugpoint.dir/bugpoint.cpp.o -o ../../bin/bugpoint -Wl,-rpath, at...

...Debugger.cpp for Release+Asserts build llvm[2]: Linking Release+Asserts executable llvm-mc (without symbols) llvm[2]: ======= Finished Linking Release+Asserts Executable llvm-lto (without symbols) make[2]: Leaving directory '/home/NIKHILREDDY/WORK/LLVM_OBJ/tools/llvm-lto' llvm[2]: Compiling ExecutionDriver.cpp for Release+Asserts build make[2]: Entering directory '/home/NIKHILREDDY/WORK/LLVM_OBJ/tools/llvm-bcanalyzer' llvm[2]: Linking Release+Asserts executable lli (without symbols) llvm[2]: Compiling llvm-bcanalyzer.cpp for Release+Asserts build llvm[2]: Compiling ExtractFunction.cpp for Rel...