search for: libtransformutils

...Analysis/CallGraph.h" Local.cpp:#include "llvm/Analysis/ConstantFolding.h" PromoteMemoryToRegister.cpp:#include "llvm/Analysis/Dominators.h" PromoteMemoryToRegister.cpp:#include "llvm/Analysis/AliasSetTracker.h" Am I right in assuming that the goal here is to get libTransformUtils to depend on nothing in libTransforms or libAnalysis? If so, its going to take some significant code rearrangement. Perhaps a lib/Analysis/Utils is in order? Please advise. Reid. On Wed, 2006-03-22 at 08:13 -0800, Reid Spencer wrote: > Okay, the problem with this cycle is LoopSimplify. It is...

Okay, the problem with this cycle is LoopSimplify. It is using AliasAnalysis which is where that _ZN4llvm11BasicAAStubEv symbol is coming from. It seems to me that LoopSimplify.cpp is in the wrong place. This file defines the LoopSimplify FunctionPass which doesn't seem to me to be a "transform util". I thought the purpose of "Transforms/Util" was to provide utilities

...thod CloneFunction from Transform/Utils/. The symbol is defined only in libLLVMTransformUtils.a so I get a linking error (undefined symbol) when I execute the module. I tried adding the LINK_LIBS_IN_SHARED and LLVMLIBS flags to the makefile but it didn't work. I guess that I can modify the LLVM libTransformUtils build so that it creates a shared object so I can load it in runtime, it doesn't seem like a proper solution. <br> </p> <p style="margin-bottom: 0cm; margin-top: 0pt;"><br> Should I be using Transform/Utils at all ? If so, why is it not linked by default and ho...

On Thu, 26 Feb 2004, Reid Spencer wrote: > One of the things that I don't understand well about LLVM is what code > is in what object files or library archives. It would be very useful if > there was a map of the dependencies between the files (e.g. if you link > X.o you need Y.a and Z.o). Trying to figure out the link lines by trial > and error is a bit frustrating. No

...sforms.a -> contains only the level raise pass libtarget.a -> contains code generator support for describing target architectures libanalysis.a -> intraprocedural analyses libipa.a -> interprocedural analyses libinstrument.a -> instrumentation (e.g. profiling) transformations libtransformutils.a -> common code shared by various xforms libregalloc.a -> sparc register allocator sched.o -> sparc instruction scheduler select.o -> sparc instruction selector support libevar.o -> live variable analysis for the sparc selectiondag.o -> start of aggressive instruction selecto...

One of the things that I don't understand well about LLVM is what code is in what object files or library archives. It would be very useful if there was a map of the dependencies between the files (e.g. if you link X.o you need Y.a and Z.o). Trying to figure out the link lines by trial and error is a bit frustrating. To assist myself with understanding this, I've started to write a