search for: libevar

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

...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 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...

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