search for: dllvm_link_llvm_dylib

...te: >> I am trying to enable this on openSUSE but it seems to break >> standalone lldb (note that we don't ship static libs): >> >> cmake -DCMAKE_C_COMPILER=clang -DCMAKE_CXX_COMPILER=clang++ >> -DCMAKE_CXX_FLAGS=-stdlib=libc++ -DLLVM_BUILD_LLVM_DYLI >> B=ON -DLLVM_LINK_LLVM_DYLIB=ON -DCMAKE_INSTALL_PREFIX=/usr >> -DCMAKE_BUILD_TYPE=RelWithDebInfo -DLLVM_LIBDIR_SUFFIX=64 -DLLDB_PA >> TH_TO_LLVM_BUILD=/usr -DLLDB_PATH_TO_CLANG_BUILD=/usr >> -DLLVM_RUNTIME_OUTPUT_INTDIR=/home/abuild/rpmbuild/BUILD/lldb-3.8.0/buil >> d/bin -DLLVM_LIBRARY_OUTPUT_INTDIR=/h...

...erally having LLVM split among that many >> dynamically loaded libraries results in significant performance regressions. > > When we first switched to cmake it was the only option to produce > shared libraries, hence we went with it. I am testing with > -DLLVM_BUILD_LLVM_DYLIB=ON -DLLVM_LINK_LLVM_DYLIB=ON atm, and will let > you know if any problem arises. I am trying to enable this on openSUSE but it seems to break standalone lldb (note that we don't ship static libs): cmake -DCMAKE_C_COMPILER=clang -DCMAKE_CXX_COMPILER=clang++ -DCMAKE_CXX_FLAGS=-stdlib=libc++ -DLLVM_BUILD_LLVM_DYLI B=O...

Are you using static linking, -DBUILD_SHARED_LIBS, or -DLLVM_LINK_LLVM_DYLIB? On Tue, Jan 8, 2019 at 7:21 AM David Greene via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Rui Ueyama <ruiu at google.com> writes: > > > I cannot reproduce this error, but this could be real. > > > > David, is this reproducible every time or is this flaky...

I am trying to build Clang/LLVM with -DLLVM_BUILD_LLVM_DYLIB=ON and -DLLVM_LINK_LLVM_DYLIB=ON to reduce the size of toolchain. I am getting LINK error 1181 about `lib\LLVM.lib` not found. After investigating, `lib\LLVM.lib` is supposed to be produced along with `bin\LLVM.dll`. `bin\LLVM.dll` is indeed produced, but it does not contain any exported symbols (10KB only) because LLVM does n...

> On Jan 14, 2016, at 11:43 AM, Ismail Donmez <ismail at i10z.com> wrote: > > On Thu, Jan 14, 2016 at 9:31 PM, Chris Bieneman via llvm-dev > <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote: >> >> On Jan 14, 2016, at 11:22 AM, Mehdi Amini <mehdi.amini at apple.com> wrote: >> >> >> On Jan 14, 2016, at 9:38

...erally having LLVM split among that many >> dynamically loaded libraries results in significant performance regressions. > > When we first switched to cmake it was the only option to produce > shared libraries, hence we went with it. I am testing with > -DLLVM_BUILD_LLVM_DYLIB=ON -DLLVM_LINK_LLVM_DYLIB=ON atm, and will let > you know if any problem arises. And one immediate "problem" shows up. I ended up with libLLVM-3.9svn.so and libclang.so libclang.so.3.9 LLVM's shared lib naming looks wrong.

On Tue, May 24, 2016 at 2:28 PM, Chris Bieneman <beanz at apple.com> wrote: > Jack, > > What version of CMake are you using? > > -Chris Chris, I am using cmake 3.5.2. My read of this problem is as follows. While libLLVM.dylib is being linked against -lxar when -DLLVM_LINK_LLVM_DYLIB:BOOL=ON is passed to cmake, the libLLVM.dylib is created with -Wl,-dead_strip such that any symbols from libxar not explicitly used with in the object files of libLLVM.dylib are stripped out. This means that those additional symbols used by llvm-objdump aren't accessible from libLLVM.dylib'...

...on openSUSE but it seems to break >>>> standalone lldb (note that we don't ship static libs): >>>> >>>> cmake -DCMAKE_C_COMPILER=clang -DCMAKE_CXX_COMPILER=clang++ >>>> -DCMAKE_CXX_FLAGS=-stdlib=libc++ -DLLVM_BUILD_LLVM_DYLI >>>> B=ON -DLLVM_LINK_LLVM_DYLIB=ON -DCMAKE_INSTALL_PREFIX=/usr >>>> -DCMAKE_BUILD_TYPE=RelWithDebInfo -DLLVM_LIBDIR_SUFFIX=64 -DLLDB_PA >>>> TH_TO_LLVM_BUILD=/usr -DLLDB_PATH_TO_CLANG_BUILD=/usr >>>> -DLLVM_RUNTIME_OUTPUT_INTDIR=/home/abuild/rpmbuild/BUILD/lldb-3.8.0/buil >>>> d/bin...

...hris Bieneman <beanz at apple.com> wrote: >> Jack, >> >> What version of CMake are you using? >> >> -Chris > > Chris, > I am using cmake 3.5.2. My read of this problem is as follows. > While libLLVM.dylib is being linked against -lxar when > -DLLVM_LINK_LLVM_DYLIB:BOOL=ON is passed to cmake, the libLLVM.dylib > is created with -Wl,-dead_strip such that any symbols from libxar not > explicitly used with in the object files of libLLVM.dylib are stripped > out. This means that those additional symbols used by llvm-objdump > aren't accessible fro...

...I needed to wrap my include via: > > #ifdef HAVE_LIBXAR > extern "C" { > #include <xar/xar.h> > } > #endif > > I think we may need some help from Chris to track this down. I’ll bug him in a bit to see if he can help us on this. While the build here with -DLLVM_LINK_LLVM_DYLIB:BOOL=ON passed on the cmake options produces HAVE_LIBXAR:INTERNAL=1 in CMakeCache.txt, I don't see anything in the cmakefiles for tools/llvm-objdump to provide the necessary linkage on the system libxar shared library. Appending the missing linkage for -lxar onto build/stage1tools/llvm-objdump/...

...wrote: >>> Jack, >>> >>> What version of CMake are you using? >>> >>> -Chris >> >> Chris, >> I am using cmake 3.5.2. My read of this problem is as follows. >> While libLLVM.dylib is being linked against -lxar when >> -DLLVM_LINK_LLVM_DYLIB:BOOL=ON is passed to cmake, the libLLVM.dylib >> is created with -Wl,-dead_strip such that any symbols from libxar not >> explicitly used with in the object files of libLLVM.dylib are stripped >> out. This means that those additional symbols used by llvm-objdump >> aren'...

...>> #ifdef HAVE_LIBXAR >> extern "C" { >> #include <xar/xar.h> >> } >> #endif >> >> I think we may need some help from Chris to track this down. I’ll bug him in a bit to see if he can help us on this. > > While the build here with -DLLVM_LINK_LLVM_DYLIB:BOOL=ON passed on > the cmake options produces HAVE_LIBXAR:INTERNAL=1 in CMakeCache.txt, I > don't see anything in the cmakefiles for tools/llvm-objdump to provide > the necessary linkage on the system libxar shared library. Appending > the missing linkage for -lxar onto > build/...

...#39;m doing wrong in my LLVM setup, or is it just slow? I'm reasonably certain I'm compiling LLVM in optimized mode, but for reference, this is my build line:     cmake .. -DCMAKE_BUILD_TYPE=Release -DLLVM_ENABLE_EH=ON -DLLVM_ENABLE_RTTI=ON -DLLVM_REQUIRES_RTTI=ON -DLLVM_ENABLE_CXX1Y=ON -DLLVM_LINK_LLVM_DYLIB=ON -DLLVM_ENABLE_FFI=ON -DLLVM_ENABLE_ASSERTIONS=ON -DLLVM_OPTIMIZED_TABLEGEN=ON -DCMAKE_INSTALL_PREFIX="/opt/llvm/install" The overall time split, from valgrind, between shared libraries in my code is:     80.48%, libLLVM-6.0.so     8.83% libc-2.23.so     2.34% libleaf_lang.so (my fro...

...ag, den 06.01.2017, 13:44 +0900 schrieb Rui Ueyama: > Hi Hahnfeld, > I just compiled with LLVM_LINK_LLVM_DYLIB enabled [1] and build lld with `ninja lld`. It built fine. What am I missing? > > [1] $ cmake -GNinja -DCMAKE_BUILD_TYPE=Debug -DLLVM_ENABLE_THREADS=On -DLLVM_ENABLE_LLD=true -DLLVM_LINK_LLVM_DYLIB=true -DLLVM_ENABLE_PROJECTS='clang;lld' ../llvm-project/llvm > > On Wed, Jan 4, 2017 at 10:31 PM, Hahnfeld, Jonas via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Hi all, > > > > > > > > I recently gave LLD a try and it definitely works fine...

...7 and not against the unversioned library. This way when we ship the new libLLVM 3.8 old application will have to be recompiled to correctly link against the new LLVM LLVM 3.7 and before did this correctly and 3.8 should not break this. As I said in another mail I tried -DLLVM_BUILD_LLVM_DYLIB=ON -DLLVM_LINK_LLVM_DYLIB=ON but it's not currently usable as it is. Thanks, ismail

...gories"' failed. [1] 25383 abort (core dumped) lld λ lldb-server : CommandLine Error: Option 'debug' registered more than once! LLVM ERROR: inconsistency in registered CommandLine options llvm is built with: cmake -G "Ninja" \ -DLLVM_BUILD_LLVM_DYLIB=ON \ -DLLVM_LINK_LLVM_DYLIB=ON \ -DCMAKE_BUILD_TYPE=RelWithDebInfo \ -DCMAKE_INSTALL_PREFIX=/usr \ -DLLVM_LIBDIR_SUFFIX=64 \ -DCMAKE_C_FLAGS="-fuse-ld=gold -fPIC" \ -DCMAKE_CXX_FLAGS="-fuse-ld=gold -fPIC" \ -DLLVM_REQUIRES_RTTI=ON \ -DLLVM_ENABLE_TIMESTAMPS=OFF \ -DLLVM_ENAB...

...>> >> Hi Hahnfeld, >> >> I just compiled with LLVM_LINK_LLVM_DYLIB enabled [1] and build lld with >> `ninja lld`. It built fine. What am I missing? >> >> [1] $ cmake -GNinja -DCMAKE_BUILD_TYPE=Debug -DLLVM_ENABLE_THREADS=On >> -DLLVM_ENABLE_LLD=true -DLLVM_LINK_LLVM_DYLIB=true >> -DLLVM_ENABLE_PROJECTS='clang;lld' ../llvm-project/llvm >> >> On Wed, Jan 4, 2017 at 10:31 PM, Hahnfeld, Jonas via llvm-dev >> <llvm-dev at lists.llvm.org> wrote: >> >> Hi all, >> >> I recently gave LLD a try and it definitely wo...

Hi all, I recently gave LLD a try and it definitely works fine. However one cannot build it together with LLVM_LINK_LLVM_DYLIB: ELF/Driver.cpp and ELF/DriverUtils.cpp pull in llvm/Support/CommandLine.h which defines the command line options so these global variables end up in libLLVM-4.0svn.so via liblldELF. If this shared library is then linked into bin/lld or bin/opt one gets errors because of

...don't know what went wrong for you. >> >> The trigger for this build failure is the usage of >> -DLLVM_BUILD_EXTERNAL_COMPILER_RT:BOOL=ON. If I drop that cmake >> option, the linkage failure for llvm-objdump disappears. > > Wrong cmake option. I meant to say that -DLLVM_LINK_LLVM_DYLIB:BOOL=ON > is the trigger of the build failure. Sorry for the noise there. Filed as https://llvm.org/bugs/show_bug.cgi?id=27855 > >> >>> >>> On Tue, May 24, 2016 at 8:07 AM, Jack Howarth via llvm-dev >>> <llvm-dev at lists.llvm.org> wrote: >>>&...

...doubt they change the configuration. > Le 20 nov. 2018 à 16:32, Jack Howarth via cfe-dev <cfe-dev at lists.llvm.org> a écrit : > > The obvious question is whether the llvm.org <http://llvm.org/> builds are using -DLLVM_ENABLE_ASSERTIONS:OFF -DCMAKE_BUILD_TYPE:STRING=Release -DLLVM_LINK_LLVM_DYLIB:BOOL=ON which would improve the load time of the compiler by combining all of the llvm libs into a single dylib and would eliminate the speed decrease from using the default use of assertions in the built compiler. > Jack > > On Tue, Nov 20, 2018 at 6:56 AM Tobias Hieta via cfe-dev...