search for: libllvmcor

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

...LLVMX86Utils.a ../../lib/libLLVMXCoreCodeGen.a ../../lib/libLLVMXCoreAsmPrinter.a ../../lib/libLLVMXCoreDesc.a ../../lib/libLLVMXCoreInfo.a ../../lib/libLLVMXCoreDisassembler.a ../../lib/libLLVMXCoreInfo.a ../../lib/libLLVMAnalysis.a ../../lib/libLLVMBitWriter.a ../../lib/libLLVMCodeGen.a ../../lib/libLLVMCore.a ../../lib/libLLVMipo.a ../../lib/libLLVMIRReader.a ../../lib/libLLVMInstCombine.a ../../lib/libLLVMInstrumentation.a ../../lib/libLLVMLinker.a ../../lib/libLLVMObjCARCOpts.a ../../lib/libLLVMScalarOpts.a ../../lib/libLLVMSupport.a ../../lib/libLLVMTarget.a ../../lib/libLLVMTransformUtils.a ../.....

(Sorry, previous post got sent by accident. This is the real one) Folks, Here's some timing results looking at LLVM when it uses libLLVMCore.o vs. libLLVMCore.a. We're trying to decide which way to go and thought some data would help. The net of it is that using libLLVMCore.a is cheaper in both time and size of executables. We save 37 seconds on linking LLVMCore and about 1 minute 30 seconds linking all the tools. The executables...

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

The recent change in the library structure to make libLLVMCore.a instead of LLVMCore.o has caused a little fallout. The problem is LLVM tools that take a --load option to load a module dynamically may now cause those modules to fail to load at runtime. This occurs because the tool with the --load option might not be linking in all of libLLVMCore.a, but only t...

Has anything been done about this issue since Reid first mentioned it? I think I'm getting bitten by it. -- John T. Reid Spencer wrote: > The recent change in the library structure to make libLLVMCore.a instead > of LLVMCore.o has caused a little fallout. The problem is LLVM tools > that take a --load option to load a module dynamically may now cause > those modules to fail to load at runtime. This occurs because the tool > with the --load option might not be linking in all of libLL...

...broken, Please see: http://llvm.org/docs/GettingStarted.html#brokengcc Please be warned as your get miss compiles and things will do strange `stuff`. As can be seen here, the reverse is true for both the GNU binutils and XPG4 versions of `nm' : -bash-3.2$ /usr/xpg4/bin/nm -p -u `find . -name libLLVMCore.a` | head ./Debug/lib/libLLVMCore.a[AsmWriter.o]: 0000000000 U __assert 0000000000 U __clzdi2 0000000000 U __udivdi3 0000000000 U __umoddi3 0000000000 U _GLOBAL_OFFSET_TABLE_ 0000000000 U _ZdaPv 0000000000 U _ZdlPv -bash-3.2$ /usr/bin/nm -p -u `find . -name libLLVMCore.a` | head ./Debug/lib/li...

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,

...e*) + 4294685040 [ 3149s] 5 libLLVMCodeGen.so 0x00003fff7f64603c [ 3149s] 6 libLLVMCodeGen.so 0x00003fff7f641f84 [ 3149s] 7 libLLVMCodeGen.so 0x00003fff7f63f16c [ 3149s] 8 libLLVMCodeGen.so 0x00003fff7f5b8220 llvm::MachineFunctionPass::runOnFunction(llvm::Function&) + 4293027568 [ 3149s] 9 libLLVMCore.so 0x00003fff7f35be3c llvm::FPPassManager::runOnFunction(llvm::Function&) + 4294119036 [ 3149s] 10 libLLVMCore.so 0x00003fff7f35c210 llvm::FPPassManager::runOnModule(llvm::Module&) + 4294119968 [ 3149s] 11 libLLVMCore.so 0x00003fff7f35c9d8 llvm::legacy::PassManagerImpl::run(llvm::...

Folks, Here's some timing results looking at LLVM when it uses libLLVMCore.o vs. libLLVMCore.a. We're trying to decide which way to go and thought some data would help. The data below was generated from using GCC 3.4.6 and binutils 2.15.92 on Fedora Core 3 running on a 2.4GHz Dual Xenon with 1GB of ram. Time With libLLVMCore.a With LLVMCore.o Link Real Time (-j 1)...

Here's the patch to build LLVM with libLLVMCore.a instead of LLVMCore.o. Could someone at Apple and someone at UIUC please try this? I want to make sure that its not just my build environment that improves with the use of libLLVMCore.a Thanks, Reid. -------------- next part -------------- A non-text attachment was scrubbed... Name: libVMCore....

.... On Thu, 2006-06-22 at 17:21 -0500, John Criswell wrote: > Has anything been done about this issue since Reid first mentioned it? > I think I'm getting bitten by it. > > -- John T. > > Reid Spencer wrote: > > > The recent change in the library structure to make libLLVMCore.a instead > > of LLVMCore.o has caused a little fallout. The problem is LLVM tools > > that take a --load option to load a module dynamically may now cause > > those modules to fail to load at runtime. This occurs because the tool > > with the --load option might not be lin...

...el::SelectAllBasicBlocks(llvm::Function const&) + 6455 13 libLLVMSelectionDAG.so 0x00007f74082d2876 llvm::SelectionDAGISel::runOnMachineFunction(llvm::MachineFunction&) + 1318 14 libLLVMCodeGen.so 0x00007f74074885dd llvm::MachineFunctionPass::runOnFunction(llvm::Function&) + 125 15 libLLVMCore.so 0x00007f740583e2ac llvm::FPPassManager::runOnFunction(llvm::Function&) + 364 16 libLLVMCore.so 0x00007f740583e52b llvm::FPPassManager::runOnModule(llvm::Module&) + 59 17 libLLVMCore.so 0x00007f740583e8d7 llvm::MPPassManager::runOnModule(llvm::Module&) + 519 1...

...: > > >>Has anything been done about this issue since Reid first mentioned it? >>I think I'm getting bitten by it. >> >>-- John T. >> >>Reid Spencer wrote: >> >> >> >>>The recent change in the library structure to make libLLVMCore.a instead >>>of LLVMCore.o has caused a little fallout. The problem is LLVM tools >>>that take a --load option to load a module dynamically may now cause >>>those modules to fail to load at runtime. This occurs because the tool >>>with the --load option might no...

...i686-pc-linux-gnu -- Threads enabled. -- Targeting X86 -- Target triple: -- Configuring done -- Generating done -- Build files have been written to: /home/selee/llvm/cmakebuild ~/llvm/cmakebuild$ make After awhile, I got the following error message and couldn't complete the build. ../../lib/libLLVMCore.a(Type.cpp.o): In function `llvm::IntegerType::get(unsigned int)': Type.cpp:(.text+0x394c): undefined reference to `llvm::sys::RWMutex::reader_acquire()' Type.cpp:(.text+0x397a): undefined reference to `llvm::sys::RWMutex::reader_release()' Type.cpp:(.text+0x3a7f): undefined reference...

On Sat, Jun 5, 2010 at 3:18 AM, Duncan Sands <baldrick at free.fr> wrote: > Hi Tom, > > I'm pretty sure that the LLVMContext constructor is defined in libLLVMCore.a > What is the output of `llvm-config --libs bitwriter`?  Does it include > -lLLVMCore? Hi Duncan, e0082888 at e0082888-laptop:~$ local/bin/llvm-config --libs bitwriter -lLLVMBitWriter -lLLVMCore -lLLVMSupport -lLLVMSystem I verified it's pulling from the right library directory, bec...

Hello Anton, While we have been discussing this, my partner discovered the source of where the sj/lj stuff is coming from. Does this mean that the LLVM libraries we're using are broken? Type.cpp ..\..\..\..\llvm\lib/libLLVMCore.a(Type.cpp.obj):Type.cpp.text+0x722): undefined reference to `__gxx_personality_sj0' ..\..\..\..\llvm\lib/libLLVMCore.a(Type.cpp.obj):Type.cpp.text+0x750): undefined reference to `_Unwind_SjLj_Register' ..\..\..\..\llvm\lib/libLLVMCore.a(Type.cpp.obj):Type.cpp.text+0x848): undefined refere...

...4603c > > [ 3149s] 6 libLLVMCodeGen.so 0x00003fff7f641f84 > > [ 3149s] 7 libLLVMCodeGen.so 0x00003fff7f63f16c > > [ 3149s] 8 libLLVMCodeGen.so 0x00003fff7f5b8220 > > llvm::MachineFunctionPass::runOnFunction(llvm::Function&) + > > 4293027568 > > [ 3149s] 9 libLLVMCore.so 0x00003fff7f35be3c > > llvm::FPPassManager::runOnFunction(llvm::Function&) + 4294119036 > > [ 3149s] 10 libLLVMCore.so 0x00003fff7f35c210 > > llvm::FPPassManager::runOnModule(llvm::Module&) + 4294119968 > > [ 3149s] 11 libLLVMCore.so 0x00003fff7f35c9d8 &...

...mbols, and says "those external to each object file" so using -g would seem redundant, The error message was as follows: "/usr/xpg4/bin/nm: -e or -g set, -u ignored". Actually it was the -u that's redundant - the -g was necessary for GenLibDeps.pl: $ nm -p -u libLLVMCore.a libLLVMCore.a[AsmWriter.o]: __asert atof _GLOBAL_OFFSET_TABLE_ isalnum ... etc ... $ nm -p -g libLLVMCore.a libLLVMCore.a[AsmWriter.o]: 0000000000 U __assert 0000000000 U atof 0000000000 U _GLOBAL_OFFSET_TABLE_ 0000000000 U isalnum The latter being what GenLibDeps.pl e...