search for: llvmobject

...xplicit linkage on libxar is required in the > tools/llvm-objdump/CMakeLists.txt when HAVE_LIBXAR and > LLVM_LINK_LLVM_DYLIB are set. > Jack Also note that this issue doesn't arise for the cmake build with -DBUILD_SHARED_LIBS:BOOL=ON because the resulting lib/Object/CMakeFiles/LLVMObject.dir/link.txt contains... /sw/src/fink.build/llvm39-3.9.0-1/opt-bin/ccclang++ -fno-common -fPIC -fvisibility-inlines-hidden -Wall -W -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wmissing-field-initializers -pedantic -Wno-long-long -Wcovered-switch-default -Wnon-virtual-dtor -Wdelete-non-virt...

...quired in the >> tools/llvm-objdump/CMakeLists.txt when HAVE_LIBXAR and >> LLVM_LINK_LLVM_DYLIB are set. >> Jack > > Also note that this issue doesn't arise for the cmake build with > -DBUILD_SHARED_LIBS:BOOL=ON because the resulting > lib/Object/CMakeFiles/LLVMObject.dir/link.txt contains... > > /sw/src/fink.build/llvm39-3.9.0-1/opt-bin/ccclang++ -fno-common -fPIC > -fvisibility-inlines-hidden -Wall -W -Wno-unused-parameter > -Wwrite-strings -Wcast-qual -Wmissing-field-initializers -pedantic > -Wno-long-long -Wcovered-switch-default -Wnon-virtua...

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

Hi! TL;DR WDYT of adding zlib decompression capabilities to LLVMObject library? ld.gold from GNU binutils has --compress-debug-sections=zlib option, which uses zlib to compress .debug_xxx sections and renames them to .zdebug_xxx. binutils (and GDB) support this properly, while LLVM command line tools don't: $ ld --version GNU gold (GNU Binutils for Ubuntu 2.22)...

On Tue, Apr 16, 2013 at 8:31 PM, Michael Spencer <bigcheesegs at gmail.com>wrote: > On Tue, Apr 16, 2013 at 2:37 AM, Alexey Samsonov <samsonov at google.com>wrote: > >> Hi! >> >> TL;DR WDYT of adding zlib decompression capabilities to LLVMObject >> library? >> > >> ld.gold from GNU binutils has --compress-debug-sections=zlib option, >> which uses zlib to compress .debug_xxx sections and renames them to >> .zdebug_xxx. >> binutils (and GDB) support this properly, while LLVM command line tools >>...

...at 8:31 PM, Michael Spencer <bigcheesegs at gmail.com> > wrote: >> >> On Tue, Apr 16, 2013 at 2:37 AM, Alexey Samsonov <samsonov at google.com> >> wrote: >>> >>> Hi! >>> >>> TL;DR WDYT of adding zlib decompression capabilities to LLVMObject >>> library? >>> >>> >>> ld.gold from GNU binutils has --compress-debug-sections=zlib option, >>> which uses zlib to compress .debug_xxx sections and renames them to >>> .zdebug_xxx. >>> binutils (and GDB) support this properly, while L...

On Tue, Apr 16, 2013 at 2:37 AM, Alexey Samsonov <samsonov at google.com>wrote: > Hi! > > TL;DR WDYT of adding zlib decompression capabilities to LLVMObject library? > > ld.gold from GNU binutils has --compress-debug-sections=zlib option, > which uses zlib to compress .debug_xxx sections and renames them to > .zdebug_xxx. > binutils (and GDB) support this properly, while LLVM command line tools > don't: > > $ ld --version &...

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 \

...segs at gmail.com> > > wrote: > >> > >> On Tue, Apr 16, 2013 at 2:37 AM, Alexey Samsonov <samsonov at google.com> > >> wrote: > >>> > >>> Hi! > >>> > >>> TL;DR WDYT of adding zlib decompression capabilities to LLVMObject > >>> library? > >>> > >>> > >>> ld.gold from GNU binutils has --compress-debug-sections=zlib option, > >>> which uses zlib to compress .debug_xxx sections and renames them to > >>> .zdebug_xxx. > >>> binutils (and...

...gt; wrote: >> >> >> >> On Tue, Apr 16, 2013 at 2:37 AM, Alexey Samsonov <samsonov at google.com> >> >> wrote: >> >>> >> >>> Hi! >> >>> >> >>> TL;DR WDYT of adding zlib decompression capabilities to LLVMObject >> >>> library? >> >>> >> >>> >> >>> ld.gold from GNU binutils has --compress-debug-sections=zlib option, >> >>> which uses zlib to compress .debug_xxx sections and renames them to >> >>> .zdebug_xxx. >>...

On 29 May 2015 at 19:06, Alexey Samsonov <vonosmas at gmail.com> wrote: > Hi everyone, > > Having proper error handling in LLVM's Object parsing library is a nice > thing by itself, but it would additionally allow us to find bugs by fuzzing > (see r238451 that adds llvm-dwarfdump-fuzzer tool), for which the clean > input validation is essential. > > This is a

...curious ones I pushed the repo to github (https://github.com/ributzka/tapi <https://github.com/ributzka/tapi>). I imagine, for example, that the reading/writing of TBD files is something that would fit better into the LLVM sources, which makes it available to other libraries and tools (e.g. LLVMObject, llvm-nm, lld, ...). I created a small patch that integrates it with llvm-nm and LLVMObject. This patch is not complete and I will split it up into smaller patches for review. I am providing it as a reference to get the discussion started. Please let me know what you think and bikeshed away :) T...

...ould use clang/llvm to build this tool. I've made good progress on OS X. Before I got too far, though. I decided to verify that I can build the code on Windows. I downloaded the 3.8.0 Windows installer from the llvm downwloads page, ran the installer, but was disappointed to see libraries like LLVMObject, LLVMBitReader, etc missing. Do I need to build LLVM from scratch on Windows to get these libraries? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20170221/a8667488/attachment.html>

...). ``` -- Looking for LLVM CMake Warning (dev) at C:/Users/me/Documents/halide/llvm-build/share/llvm/cmake/LLVMExports.cmake:232 (set_target_properties): Syntax error in cmake code at C:/Users/me/Documents/halide/llvm-build/share/llvm/cmake/LLVMExports.cmake:233 when parsing string LLVMObject;LLVMSupport;C:\Program Files (x86)\Microsoft Visual Studio 14.0\DIA SDK\lib\diaguids.lib Invalid escape sequence \P Policy CMP0010 is not set: Bad variable reference syntax is an error. Run "cmake --help-policy CMP0010" for policy details. Use the cmake_policy command to set t...

...c). For > the curious ones I pushed the repo to github ( > https://github.com/ributzka/tapi). > > I imagine, for example, that the reading/writing of TBD files is something > that would fit better into the LLVM sources, which makes it available to > other libraries and tools (e.g. LLVMObject, llvm-nm, lld, ...). > > I created a small patch that integrates it with llvm-nm and LLVMObject. > This patch is not complete and I will split it up into smaller patches for > review. I am providing it as a reference to get the discussion started. > > Please let me know what you t...

On Fri, May 29, 2015 at 4:06 PM, Alexey Samsonov <vonosmas at gmail.com> wrote: > Hi everyone, > > Having proper error handling in LLVM's Object parsing library is a nice > thing by itself, but it would additionally allow us to find bugs by fuzzing > (see r238451 that adds llvm-dwarfdump-fuzzer tool), for which the clean > input validation is essential. > > This

On 06/18/2015 06:46 PM, Dan Liew wrote: >> The issue is the that that generated LLVMExports.cmake file has this in it >> INTERFACE_LINK_LIBRARIES "LLVMObject;LLVMSupport;C:\Program Files (x86)\Microsoft Visual Studio 14.0\DIA SDK\lib\diaguids.lib" > > Hmm actually this might be a bug in the > ``/lib/DebugInfo/PDB/CMakeLists.txt`` file. CC'ing Zach Turner seeing > as he appears to be the author. > > - set(LIBPDB_ADDITIONAL_LI...

Hi everyone, I'm working on a library for runtime introspection of C++ programs, for example, getting stack traces, decorating logs with source file information, etc. It currently uses LLVMObject and LLVMDebugInfo. There's a feature I want to add, but it requires that I understand where on the stack local variables are located. For this to work on x86-64, I would need to do whole "virtual unwinding" thing, i.e., create a library that can understand the DWARF call frame infor...

...linking all that stuff with user code results in symbol name conflicts. We've come up with what seems to be a perfect solution (thanks to a Chandler's advice at the recent developer meeting). We build everything down to (but not including) libc into LLVM bitcode. This includes LLVMSupport, LLVMObject, LLVMDebugInfo, libc++, libc++abi, zlib (!). Then we bundle it all together and internalize all non-interface symbols: llvm-link && opt -internalize. Then compile down to a single object file. This results in a perfect isolation of symbolizer internals. One drawback is that this requires s...

With comdats parts of the file might never be read. There are also multiple levels of cache and while all the relocations of a file will fit in ram, it is probably still more efficient to validate them as they are read. But I think (typing on a phone) that relocations are another case where the best is to have a more specific api: the only way the relocation is invalid from the perspective of