search for: libllvmipa

Hello Anton Thu, 3 Aug 2006 15:06:56 +0400 you wrote: > here it is in the attachment :) Ok. Could you also send LibDeps.txt file? It should be in /obj/tools/llvm-config directory -- With best regards, Anton Korobeynikov. Faculty of Mathematics & Mechanics, Saint Petersburg State University.

...ad of always having both or none. > I don't know enough about the codegen/target/analysis/ipa stuff to be > able to make any suggestions. Perhaps Chris can shed some light. >> LLVMCodeGen.o LLVMSelectionDAG.o libLLVMAnalysis.a libLLVMTarget.a >> libLLVMTransformUtils.a libLLVMipa.a Codegen and SelectionDAG can be merged, either physically in the source base or treated as one thing in your code. CodeGen should depend on Target, but not the other way around. LLVMIPA should depend on LLVMAnalysis, but certainly nothing in the list should depend on LLVMIPA. If you knew wha...

...ency data to utils/llvm- config/LibDeps.txt. There are three sets of circular dependencies between LLVM libraries. If you use any library from one of these sets, you may need to pull in the rest: LLVMCodeGen.o LLVMSelectionDAG.o libLLVMAnalysis.a libLLVMTarget.a libLLVMTransformUtils.a libLLVMipa.a LLVMSparcV9.o LLVMSparcV9InstrSched.o LLVMSparcV9ModuloSched.o LLVMSparcV9RegAlloc.o LLVMExecutionEngine.o LLVMInterpreter.o LLVMJIT.o The first set is the most problematic: It includes four *.a files, which means that certain linkers will tend to get confused unless you repeat ...

...efer to individual instruction. > I followed the conventions used in GlobalModRefPass, which is also > an extension of ModulePass. Is there any other convention which > needs to be followed? > I would think that that is enough. Where are you adding this module? Is it part of the libLLVMipa.a library? Or is it another library? Make sure that when you link your application, you're analysis is either part of libLLVMipa.a or has that library on the link line. -bw

...to add alias analysis in llvm. I created a file ProfileAlias.cpp in llvm source at the place where Andersens.cpp is there. ProfileAlias.cpp does nothing at present just empty definitions of required functions. When I build llvm I get the following error: /home/ambika/llvm1/llvm-obj/Release/lib/libLLVMipa.a(ProfileAlias.o): In function `llvm::createProfileAliasPass()': ProfileAlias.cpp:(.text+0x46): undefined reference to `vtable for ProfileAlias' /home/ambika/llvm1/llvm-obj/Release/lib/libLLVMipa.a(ProfileAlias.o): In function `llvm::Pass* llvm::callDefaultCtor<ProfileAlias>()'...

Hi, I have made my optimization as an extension of ModulePass as suggested in last mail. I included "addRequired<CallGraph>" in getAnalysisUsage function. The application compiles fine but while linking, I get following errors: "undefined reference to llvm::CallGraphLinkVar" "undefined reference to llvm::CallGraph::ID The above error is at point where I refer to

...bDeps.txt. > > There are three sets of circular dependencies between LLVM libraries. > If you use any library from one of these sets, you may need to pull > in the rest: > > LLVMCodeGen.o LLVMSelectionDAG.o libLLVMAnalysis.a libLLVMTarget.a > libLLVMTransformUtils.a libLLVMipa.a > > LLVMSparcV9.o LLVMSparcV9InstrSched.o LLVMSparcV9ModuloSched.o > LLVMSparcV9RegAlloc.o > > LLVMExecutionEngine.o LLVMInterpreter.o LLVMJIT.o > > The first set is the most problematic: It includes four *.a files, > which means that certain linkers will ten...

Hi, I am not making this application part of LLVM library although I do link the libLLVMipa library ( actually I am using llvm-config --libs all option in the Makefile which links all the libraries). Is it necessary to make it part of LLVM library? Thanks for you responses. --Kapil On Fri, Aug 22, 2008 at 3:40 PM, Bill Wendling <isanbard at gmail.com> wrote: > On Aug 21, 20...

Hello Anton Fri, 4 Aug 2006 21:45:19 +0400 you wrote: > Written by Mike Haertel and Paul Eggert. > I've updated llvm and llvm-gcc4 ant trying to build it again after > PR845 was resolved. According to Reid's letter this PR coud be the > reason of my problem. Anyway, "sort" call can cause large problems depending, where in your PATH cygwin directory is (before

Hi! On 02.02.2010, at 20:16, ambika wrote: > /home/ambika/llvm1/llvm-obj/Release/lib/ > libLLVMipa.a(ProfileAlias.o): In > function `llvm::createProfileAliasPass()': > ProfileAlias.cpp:(.text+0x46): undefined reference to `vtable for > ProfileAlias' http://gcc.gnu.org/faq.html#vtables Does that help? Andi

...8a62a67000) libLLVMInstCombine.so.3.7 => /lib64/libLLVMInstCombine.so.3.7 (0x00007f8a627aa000) libLLVMInstrumentation.so.3.7 => /lib64/libLLVMInstrumentation.so.3.7 (0x00007f8a6253f000) libLLVMTransformUtils.so.3.7 => /lib64/libLLVMTransformUtils.so.3.7 (0x00007f8a6226b000) libLLVMipa.so.3.7 => /lib64/libLLVMipa.so.3.7 (0x00007f8a62043000) libLLVMX86Desc.so.3.7 => /lib64/libLLVMX86Desc.so.3.7 (0x00007f8a61c95000) libLLVMMCDisassembler.so.3.7 => /lib64/libLLVMMCDisassembler.so.3.7 (0x00007f8a61a8f000) libLLVMX86Info.so.3.7 => /lib64/libLLVMX86Info.so.3.7 (...

> > If you're building llvm-gcc4, you don't need the runtime libraries, so > I'd just stick with the "tools-only" build and declare success. If > you're building llvm-gcc3, I'd suggest you switch to llvm-gcc4 :) I switched to llvm-gcc4 but when I run make from obj folder i run into folowing errors: Can't find a library with no dependencies at

Hello Anton Thu, 3 Aug 2006 12:38:54 +0400 you wrote: > I've updated it yesterday and rebuilt - llvm built fine. But when > building llvm-gcc4 (also updated yesterday from new /trunk > directory) it fails with the same error. You might easily get llvm-gcc4-mingw32 binaries from "prerelease" directory. Since stdcall, fastcall & dllimport stuff is unsupported right now,

Simon Burton <simon at arrowtheory.com> writes: >> There are several possibilities here: either add1 is assigned a NULL >> pointer, or LLVM was unable to use the JIT and generates bytecode >> instead of native code, or invalid native code was generated >> (unlikely). > > Well, it's not NULL: > > (gdb) print add1 > $1 = (int (*)(int)) 0x83e43b8 >

...m config --libs jit asmparser" it compiles but segfaults in the usual place. Here are the libs it uses in this case: $ llvm-config --libnames jit asmparser LLVMAsmParser.o LLVMJIT.o LLVMExecutionEngine.o LLVMCodeGen.o LLVMSelectionDAG.o libLLVMAnalysis.a libLLVMTarget.a libLLVMTransformUtils.a libLLVMipa.a libLLVMAnalysis.a libLLVMTarget.a libLLVMTransformUtils.a libLLVMipa.a LLVMCore.o libLLVMSupport.a libLLVMSystem.a LLVMbzip2.o Somewhat better is when I use "--libs engine asmparser". It works, and generates an exe around 77Mb. And no complaints when linking. thanks for your help Osc...

...eader file. I tried using FunctionPassManager but it does not implement getOnTheFlyPass() required by getAnalysis(). I also tried putting CGPassManager in PassManager.cpp (and therefore in libLLVMCore.a ?) but the build failed due to a cyclic dependency between libLLVMCore.a, libLLVMAnalysis.a and libLLVMipa.a. Any pointers to resolving this would be greatly appreciated. Thanks in advance, Pranav Qualcomm Innovation Center, Inc is a member of the Code Aurora Forum.

On Mar 21, 2006, at 11:23 PM, Chris Lattner wrote: >>> LLVMCodeGen.o LLVMSelectionDAG.o libLLVMAnalysis.a >>> libLLVMTarget.a >>> libLLVMTransformUtils.a libLLVMipa.a > > CodeGen should depend on Target, but not the other way around. > LLVMIPA should depend on LLVMAnalysis, but certainly nothing in the > list should depend on LLVMIPA. If you knew what was pulling in IPA > that would probably be an easy tie to sever. > > Ideally, none...

...oing to validate that shortly. Reid. On Wed, 2006-03-22 at 09:26 -0500, Eric Kidd wrote: > On Mar 21, 2006, at 11:23 PM, Chris Lattner wrote: > >>> LLVMCodeGen.o LLVMSelectionDAG.o libLLVMAnalysis.a > >>> libLLVMTarget.a > >>> libLLVMTransformUtils.a libLLVMipa.a > > > > CodeGen should depend on Target, but not the other way around. > > LLVMIPA should depend on LLVMAnalysis, but certainly nothing in the > > list should depend on LLVMIPA. If you knew what was pulling in IPA > > that would probably be an easy tie to sever....

...ib/libLLVMTestInfo.a lib/libLLVMMC.a lib/libLLVMMCParser.a lib/libLLVMSupport.a lib/libLLVMAsmPrinter.a lib/libLLVMSelectionDAG.a lib/libLLVMCodeGen.a lib/libLLVMScalarOpts.a lib/libLLVMInstCombine.a lib/libLLVMProfileData.a lib/libLLVMObject.a lib/libLLVMBitReader.a lib/libLLVMTransformUtils.a lib/libLLVMipa.a lib/libLLVMAnalysis.a lib/libLLVMTarget.a lib/libLLVMCore.a lib/libLLVMTestAsmPrinter.a lib/libLLVMMCParser.a lib/libLLVMMC.a lib/libLLVMSupport.a -lrt -ldl -ltinfo -lpthread -lz -lm -Wl,-rpath,"\$ORIGIN/../lib" && : lib/libLLVMTestAsmParser.a(TestAsmParser.cpp.o): In function `...

On Fri, 14 Apr 2006 03:25:39 +0200 Oscar Fuentes <oscarfv at telefonica.net> wrote: ... > Simon, > > With a fresh CVS checkout, I've tried your test case on Windows/VC++ > and it works ok. Too bad that I have not access to a Linux machine > right now. I'll like to see what's wrong with your test case. > > What you get from running the test case under gdb