search for: llvmsparc

Hi Eric, Its definitely amusing :) About the only thing I can suggest are: 1. Combine LLVMSparc*.o into one LLVMSparc.a. That work is already happening with the new Sparc backend that is being developed. Should be out in 1.7 (Chris?) 2. Combine the JIT/Interpreter/ExecutionEngine into one .a I don't know enough about the codegen/target/analysis/ipa stuff to be able to make any suggesti...

...s/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 '-l' flags...

...LLVMTARGETOBJCMD := case $(target) in \ alpha-*-*) echo LLVMAlpha.o;; \ ia64-*-*) echo LLVMIA64.o;; \ i[34567]86-*-*) echo LLVMX86.o;; \ powerpc*-*-*) echo LLVMPowerPC.o;; \ sparc-*-*) echo LLVMSparc.o;; \ sparcv9-*-*) echo LLVMSparc.o;; \ esac LLVMTARGETOBJ := $(shell $(LLVMTARGETOBJCMD)) ifeq ($(LLVMTARGETOBJ),) $(error Unsuported LLVM Target $(target)) endif LLVMLIBS = -L$(LLVMLIBPATH) $(LLVMLIBPATH)/$(LLVMTARGETOBJ) -lLLVMScalarOpts \...

...stall/lib/LLVMCBackend.o /home/rich/llvm-install/lib/LLVMCellSPU.o /home/rich/llvm-install/lib/LLVMMips.o /home/rich/llvm-install/lib/LLVMARM.o /home/rich/llvm-install/lib/LLVMIA64.o /home/rich/llvm-install/lib/LLVMAlpha.o /home/rich/llvm-install/lib/LLVMPowerPC.o /home/rich/llvm-install/lib/LLVMSparc.o /home/rich/llvm-install/lib/LLVMX86.o -lLLVMSelectionDAG -lLLVMCodeGen -lLLVMScalarOpts -lLLVMTransformUtils -lLLVMipa -lLLVMAnalysis -lLLVMTarget -lLLVMCore -lLLVMSupport -lLLVMSystem Does this sort of thing ring a bell with anyone? -Rich

On Mar 10, 2006, at 2:57 PM, Martin Pärtel wrote: > I'm currently using the "make install"-ed version of LLVM in an > autoconf/automake project. Setting it up wasn't that bad really. > The .a > libraries can be statically linked with the -l flag and .o > libraries are > simply linked in as normal object files (without -l). All the > libraries got >

On Tue, 21 Mar 2006, Reid Spencer wrote: > About the only thing I can suggest are: > > 1. Combine LLVMSparc*.o into one LLVMSparc.a. That work is already > happening with the new Sparc backend that is being developed. Should be > out in 1.7 (Chris?) I wouldn't worry about the SparcV9 backend for your project. > 2. Combine the JIT/Interpreter/ExecutionEngine into one .a I'd much rathe...

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.

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

...-- llvm-1.7~/llvm-gcc4-1.7.source/gcc/Makefile.in 2006-04-19 15:51:47.000000000 -0600 +++ llvm-1.7/llvm-gcc4-1.7.source/gcc/Makefile.in 2006-07-09 20:29:57.000000000 -0600 @@ -827,6 +827,7 @@ powerpc*-*-*) echo LLVMPowerPC.o;; \ sparc-*-*) echo LLVMSparc.o;; \ sparcv9-*-*) echo LLVMSparc.o;; \ + x86_64-*-*-*) echo LLVMCBackend.o;; \ esac LLVMTARGETOBJ := $(shell $(LLVMTARGETOBJCMD)) ---------------------------------------------------------------------- Yes, it is a hack, but it does let...

...uilding the bindings against an installed llvm-config. LLVMers, what's the advantage to building .o files instead of .a's for these libs? LLVMARM.o LLVMAlpha.o LLVMCBackend.o LLVMCellSPU.o LLVMExecutionEngine.o LLVMIA64.o LLVMInterpreter.o LLVMJIT.o LLVMMSIL.o LLVMMips.o LLVMPowerPC.o LLVMSparc.o LLVMX86.o This wouldn't be a problem if these components used .a's instead, since ld's search paths are set up correctly. The options I see are: Use archive libraries instead of objects for the above. Link the above .o files into .a's just for the ocaml bindings. Kind of st...

I've run into a problem with the ocaml bindings and the jit. It builds fine without the jit, but when I try to include it it tries to use the c object files from the build location, instead of the install location: > llvm-config --libdir --libfiles engine /opt/local/lib /opt/local/lib/LLVMX86.o /opt/local/lib/libLLVMSelectionDAG.a /opt/local/lib/libLLVMCodeGen.a

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