similar to: [LLVMdev] why not the binary files: clang clang-check clang-format llvm-tblgen clang-tblgen link to the shared common library to save space.

Displaying 20 results from an estimated 30000 matches similar to: "[LLVMdev] why not the binary files: clang clang-check clang-format llvm-tblgen clang-tblgen link to the shared common library to save space."

2016 Jan 25
3
Why do we static link all llvm libraries in every executable?
Hi I found basically all llvm libraries are statically linked into each executable and LLVMgold.so, This make the clang/llvm package larger and larger with a lot of duplicated code. If I build debug version, the disk space required is even larger. Is there any particular reason to keep doing this way? If we separate several shared libraries something like libclang.so, libllvm.so and let
2016 Jan 14
2
Building SVN head with CMake - shared libraries?
Now that autoconf is going away soon, I figured I'd try building using CMake. I checked out llvm, cfe and lldb from the SVN server, and followed the basic build instructions. cmake -DBUILD_SHARED_LIBS=OFF -DCMAKE_INSTALL_PREFIX=/tools/llvm/svn_head -DLLVM_TARGETS_TO_BUILD="X86;CppBackend" -DCMAKE_BUILD_TYPE=Release -DLLVM_ENABLE_ASSERTIONS=ON ../llvm Everything worked well, and in
2016 Jan 14
4
Building SVN head with CMake - shared libraries?
Thanks - I'll try this tonight. Assuming it works, should these variables be added to the docs at http://llvm.org/docs/CMake.html ? On Wed, Jan 13, 2016 at 10:26 PM, Andrew Wilkins <axwalk at gmail.com> wrote: > > > On Thu, 14 Jan 2016 at 11:02 David Jones via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > >> Now that autoconf is going away soon, I
2012 Aug 16
2
[LLVMdev] libclang parsing bug
Hey everyone, first of all I just wanted to say thanks :) I've been using libclang for building my own C/C++ IDE and its great. I have, however discovered a bug (which I already submitted on llvm bugzilla but I got the impression that no one reads that :)). If I try to use clang_parseTranslationUnit on this code below: int main() { return reinterpret_cast libclang crashes. This is the code
2016 Jan 15
2
Building SVN head with CMake - shared libraries?
On Fri, Jan 15, 2016 at 11:05 AM, Ismail Donmez <ismail at i10z.com> wrote: > Hi, > > On Fri, Jan 15, 2016 at 12:59 AM, Chris Bieneman <beanz at apple.com> wrote: >> I’m kinda scared that you’re using it. What are you trying to accomplish >> that you are using it? Generally having LLVM split among that many >> dynamically loaded libraries results in
2017 Sep 03
0
Why are LLVM releases statically linked against LLVM libraries?
On 3 Sep 2017, at 02:41, Will Dietz via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > I can speculate the reasons from a technical standpoint and by > inferring from commit history... > but curious if there's a better answer to be had? There’s a fairly noticeably performance improvement from static linking. I think last time I benchmarked it, building FreeBSD with
2020 May 21
1
[llvm][llvm-tblgen][clang-tblgen] MSVC Debug ill-build of clang-tblgen.exe and llvm-tblgen.exe
Hi, everyone. Does anyone faced with the MSVC Debug build issues of clang-tblgen and llvm-tblgen? I'm using Windows10 Pro. MSVC and GCC. Here is my cmake setup: cmake -GNinja ../llvm -DLLVM_ENABLE_PROJECTS=clang -DLLVM_TARGETS_TO_BUILD=X86 -DCMAKE_BUILD_TYPE=Debug When building debug with GCC, cmd shows next: D:\llvm-project\buildn2\bin>clang-tblgen.exe --version LLVM
2020 Jan 11
2
Unresolved dependencies when upgrade on centOS 8
Hi, Guys i got unresolved dependencies when trying to upgrade centOS 8, what should i do to fix this? [root at ws1 ebedsat]# dnf upgrade Last metadata expiration check: 0:14:27 ago on Sat 11 Jan 2020 12:16:02 PM WIB. Error: Problem 1: cannot install the best update candidate for package kmod-iwlegacy-0.0-1.el8.elrepo.x86_64 - nothing provides kernel >= 4.18.0-147.el8 needed by
2013 May 22
0
[LLVMdev] Linking Debug+Asserts Shared Library libclang.so: final link failed: Bad value
> From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On Behalf Of Raghavendra K > Subject: [LLVMdev] Linking Debug+Asserts Shared Library libclang.so: final link failed: Bad value > llvm[4]: Linking Debug+Asserts Shared Library libclang.so > /usr/lib64/gcc/x86_64-suse-linux/4.1.2 You might want to consider trying a version of gcc that's less than six
2013 May 22
2
[LLVMdev] Linking Debug+Asserts Shared Library libclang.so: final link failed: Bad value
Hi, I downloaded latest 3.2 release of llvm and clang. used configure to generate the make files options used: ../configure --enable-debug-symbols=yes --enable-keep-symbols=yes --enable-pic=yes --enable-keep-symbols=yes --enable-debug-runtime=yes --enable-optimized=no --enable-targets=x86 --enable-embed-stdcxx=yes --enable-jit=no CXXFLAGS=-fPIC CFLAGS=-fPIC Now i get this strange error,cannot
2016 Apr 18
3
GVN pass limitation.
Hello, We are now facing a bug caused by the GVN pass, only part of the code was optimized. I have found that the problem is cause by an Limit in lib/Analysis/MemoryDependenceAnalysis.cpp 00055 static cl::opt<unsigned> BlockScanLimit( 00056 "memdep-block-scan-limit", cl::Hidden, cl::init(100), 00057 cl::desc("The number of instructions to scan in a block in
2017 Sep 03
2
Why are LLVM releases statically linked against LLVM libraries?
Sincere question! I'm not at all suggesting this is the wrong choice or asking it to be defended, just explained :) Simply curious if anyone can speak as to the reasons for this and perhaps give a sense of how strong these reasons are or if they're just the tie-breaking reasons we came up with because hosting /both/ seemed silly :P. (or whatever the case may be) I'll note the build
2020 Apr 23
7
Cannot build master
Hi, Using master at b0a1c0b72c9c61f8b0a223e08f43498abb64f5e8, I cannot build LLVM. I configured with: CC=clang CXX=clang++ cmake -DCMAKE_INSTALL_PREFIX=$HOME/opt/llvm11-git \ -DCMAKE_BUILD_TYPE=Release \ -DLLVM_BUILD_LLVM_DYLIB=ON \ -DLLVM_LINK_LLVM_DYLIB=ON \ -DBUILD_SHARED_LIBS=OFF \ -DLLVM_ENABLE_EH=ON \ -DLLVM_ENABLE_RTTI=ON \
2004 Dec 14
2
[LLVMdev] Linking tblgen: undefined reference to `llvm::sys::Path::Path(std::string)'
Hi, I'm linking tblgen. However, I get below error. I can't figure out what's wrong here. Could it be this statement in the Path.h: mutable std::string path; ///< Storage for the path name. ------------------ llvm[2]: Linking Debug executable tblgen c:/projects/build/MinGW/llvm-1-1/utils/TableGen/Debug/TableGen.o(.text+0x19da): In function `main':
2014 Apr 30
2
[LLVMdev] Ubuntu 14.04 Trusty packages broken
Hello, I don't know how it happened, but recent Ubuntu builds have broken -dev packages, which contain same libraries as non-dev packages. dpkg: error processing archive /var/cache/apt/archives/libllvm3.5_1%3a3.5~svn207603-1~exp1_amd64.deb (--unpack): trying to overwrite '/usr/lib/llvm-3.5/lib/libLLVM-3.5.so', which is also in package llvm-3.5-dev 1:3.5~svn207603-1~exp1 dpkg:
2004 Dec 14
0
[LLVMdev] Linking tblgen: undefined reference to `llvm::sys::Path::Path(std::string)'
On Tue, 14 Dec 2004, Henrik Bach wrote: > llvm[2]: Linking Debug executable tblgen > c:/projects/build/MinGW/llvm-1-1/utils/TableGen/Debug/TableGen.o(.text+0x19da): > In function `main': > c:/projects/src/llvm-1/llvm/utils/TableGen/TableGen.cpp:429: undefined > reference to `llvm::sys::Path::Path(std::string)' > collect2: ld returned 1 exit status > make[2]: ***
2004 Dec 14
1
[LLVMdev] Linking tblgen: undefined reference to `llvm::sys::Path::Path(std::string)'
Yeah, that's confirmed. Make sure you update include/llvm/System/Path.h and the contents of lib/System then make clean and rebuild. Should fix it Reid. On Tue, 2004-12-14 at 11:10, Chris Lattner wrote: > On Tue, 14 Dec 2004, Henrik Bach wrote: > > llvm[2]: Linking Debug executable tblgen > > c:/projects/build/MinGW/llvm-1-1/utils/TableGen/Debug/TableGen.o(.text+0x19da): >
2012 Jun 21
0
[LLVMdev] is configure+make dead yet?
On 06/21/2012 04:22 PM, Óscar Fuentes wrote: > About the "many features" that cmake lacks, can you provide a list, > please? Generally it works fairly well, but here are some differences to the autoconf-based build I noticed: - No 'make uninstall'. That is a real deal breaker if you want to quickly try a new LLVM version. I know that cmake doesn't provide this out of
2015 Jul 08
2
[LLVMdev] [cfe-dev] Building clang + libc++ + libc++abi
If your cut-n-paste is accurate, you seem to be missing a closing quote for CMAKE_CXX_LINK_FLAGS. hth... don On Jul 8, 2015 2:22 AM, "David A. Greene" <greened at obbligato.org> wrote: > greened at obbligato.org (David A. Greene) writes: > > > I looked at the instructions on the libc++ page and for Linux it > > recommends building with -stdlib=libc++ -lc++abi.
2013 Feb 07
0
[LLVMdev] [llvm-tblgen] Two issues: crash case and mysterious double-inclusion case
On Wed, Feb 06, 2013 at 11:47:31PM +0100, Dmitry Mikushin wrote: > Dear all, > > I need your help to understand weird llvm-tblgen behavior. Please take your > favourite version of llvm-tblgen and use it in the root directory of the > archive attached in both bug reports: > > http://llvm.org/bugs/show_bug.cgi?id=15188 > http://llvm.org/bugs/show_bug.cgi?id=15189 $