search for: profpaths

...are all prefixed with LLVM 2. They use upper and lower case to match the library directory they came from. In general they should be recognizable to you. For example: libtarget.a -> libLLVMTarget.a However, a few of them changed outright to make it consistent: cwriter.o -> LLVMCBackend.o profpaths.o -> LLVMProfilePaths.o Sparcv9Sched.o -> LLVMSparcV9InstrSched.o The changes have all been made to the necessary makefiles in llvm proper, but not in any of the projects. The adjustment should be pretty straight forward: capitalize first letters and prefix with LLVM. Reid.

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

...mon 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 selector for DAGs profpaths.o -> path profiling instrumentation Basically, libraries are built in two forms: .a files and .o files. .o files are built/used when client programs want to link in _everything_ in a library. .a files are used when a client program wants to use some of the stuff in a library, based on what s...

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