search for: lunwind

On 1/30/15 1:17 PM, Saleem Abdulrasool wrote: > Although this has been discussed in the past, I think that given a few > conversations, it seems that it unfortunately needs to be brought up again. > > There seems to be some disagreement over the ideal location of the > unwinder (libunwind). Currently, libunwind resides in a subdirectory of > libc++abi. There seems to be some

...(modulo bug fixes) for stability and we will want a new clang, lld, and lldb to work with the old ones. My problem, and I'll be quick not to digress too much, is that --rtlib=compiler-rt is slightly broken. I can't assume libunwind or libc++abi are there, so for rtlib=RT, I don't add -lunwind and -lc++abi "as needed" like we do for libgcc's counterparts. This breaks expectations more than implementations. To use compiler-rt I need to also add -lgcc_s or -lunwind, and that's not obvious. A warning here would be weird. Again, I totally agree it's not a hard require...

...*** This is the patch that changed the configuration: http://llvm.org/viewvc/llvm-project?view=revision&revision=274747 and the only thing I can think could have caused it is the change in librry order: - lit_extra_opts={'link_flags': '"-lc++abi -lc -lm -lpthread -lunwind -ldl -L/opt/llvm/lib/clang/3.6.0/lib/linux -lclang_rt.builtins-arm"'}, + lit_extra_opts={'link_flags': '"-lc++abi -lpthread -lunwind -ldl -lc -lm -L/opt/llvm/lib/clang/3.6.0/lib/linux -lclang_rt.builtins-arm"'}, Any ideas? cheers, -renato

...this configurable via a different set of flags? No. I believe this is an old flag when that wasn't enable by default (and now it's used to disable it if you have the dirs). But maybe heavier users of libc++ can help you there. You still have to use LDFLAGS="--stdlib=libc++ -lc++abi -lunwind" and, if you're not installing it anywhere (but using the build directory), add LD_LIBRARY_PATH=build/lib to your environment. If you run into inconsistencies because libgcc_s / libgcc_eh are included, or if libstdc++ is included as well, you may have to use -nostdlibc++ to clean up the i...

...s from libc++abi and compiler-rt > 2.1 OPTIONAL 1: err if libunwinder is not there, clang errs if rtlib=RT > 2.2 OPTIONAL 2: warns if libunwind is not there, clang errs if rtlib=RT > 2.3 OPTIONAL 3: nothing, make clang smarter to pick existing unwinder > 3. Change clang to assume -lunwind when --rtlib=compiler-rt > 3.1 OPTIONAL 4: allow linker error if no -lunwind / -lgcc_s > 3.2 OPTIONAL 5: Add option to change unwinder library by not adding > -lunwind/-lgcc_s, but whatever comes as argument > > 1, 2, and 3 must be changed. > > I vote for adding { 2.2, 3.1...

...he actually wanted the resulting compiler to use libc++ Sorry for the noise Michael In short Michael it should not matter if clang was build with libc++ or libstdc++ the resulting compiler can use both after the fact As Renato described above in more detail LDFLAGS="--stdlib=libc++ -lc++abi -lunwind" would be used to tell that resulting compiler to link its programs with libc++, libc++abi and libunwind Rather than using libstdc++ and libgcc_eh If you want to know how to change the default to do this without touching the LDFLAGS for your target this you must look in the clang repo under l...

On 28 Jul 2016, at 15:30, Renato Golin <renato.golin at linaro.org> wrote: > > My problem, and I'll be quick not to digress too much, is that > --rtlib=compiler-rt is slightly broken. I can't assume libunwind or > libc++abi are there, so for rtlib=RT, I don't add -lunwind and > -lc++abi "as needed" like we do for libgcc's counterparts. > > This breaks expectations more than implementations. To use compiler-rt > I need to also add -lgcc_s or -lunwind, and that's not obvious. A > warning here would be weird. > > Again, I totall...

...stem that I want to build with this toolchain is Linux-based, but not GNUish. I would like to use musl instead of glibc and libc++ instead of libstdc++, only use binutils provided by LLVM. I think that in that case I will link libc++abi and libunwind to libc++ statically, so I will not have to add -lunwind and -lc++abi to my LDFLAGS. Is it okay to do that? There is an experimental LIBCXX_ENABLE_STATIC_ABI_LIBRARY option, I will try to enable it. > > The host system that I'm compiling on is Alpine Linux (musl-based distro), if it matters. It probably makes sense for libc++abi or libcxxrt,...

Hi, I am wondering about the meaning of the cmake flags LLVM_ENABLE_LIBCXX and LLVM_ENABLE_LIBCXXABI. Are they used to indicate that if the C/C++ compiler for building LLVM is clang, and if this clang has support for libc++ with libc++Abi, that both lib++ and libc++abi should be used (instead of linking to the default, which at least on Linux is libstdc++)? If not, what is the canonical way of

On 5 Jun 2017, at 15:17, Jonathan Roelofs via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > On 6/5/17 5:17 AM, Dmitry Golovin via llvm-dev wrote: >> I'm trying to build LLVM, Clang, LLD, compiler-rt, libc++, libc++abi and libunwind with musl-based toolchain. >> >> The configuration is the following: >> >> LIBCXX_HAS_MUSL_LIBC=ON >>

On 28 Jul 2016, at 08:59, Renato Golin <renato.golin at linaro.org> wrote: > > On 28 Jul 2016 8:36 a.m., "David Chisnall via llvm-dev" <llvm-dev at lists.llvm.org> wrote: > > This does not apply to libc++. We support building the entire LLVM suite with other C++ standard library implementations (at least libstdc++, and I think also with Visual Studio’s

On 28 Jul 2016 8:36 a.m., "David Chisnall via llvm-dev" < llvm-dev at lists.llvm.org> wrote: > This does not apply to libc++. We support building the entire LLVM suite with other C++ standard library implementations (at least libstdc++, and I think also with Visual Studio’s implementation), so there is no dependency of anything on libc++. Similarly, we support building libc++

Hi, I am trying to use LLVM/clang to build a binary for ARM Cortex M platforms. When I build my binary the linker fails to find these libraries. ./bin/clang++ -target arm-none-eabi -mcpu=cortex-m4 ./temp.cpp -L ./lib/ -L ./libexec/ -L ../build3_v7m/lib/ ld.lld: error: unable to find library -lunwind ld.lld: error: unable to find library -lc ld.lld: error: unable to find library -lm ld.lld: error: unable to find library -lclang_rt.builtins-arm.a I am guessing I can borrow libraries such as lc and lm from GCC arm-none-eabi*, but for clang_rt.builtins-arm.a (which I thought should've been bu...

Although this has been discussed in the past, I think that given a few conversations, it seems that it unfortunately needs to be brought up again. There seems to be some disagreement over the ideal location of the unwinder (libunwind). Currently, libunwind resides in a subdirectory of libc++abi. There seems to be some desire from multiple parties that it be moved into compiler-rt or a separate

...he unwinding functionality is already built into the operating > > system, > > available via the Rtl*Unwind* functions. > > > > > > Martin, > > you mean these functions > > > https://docs.microsoft.com/en-us/windows/win32/api/winnt/nf-winnt-rtlunwind > > > > > https://docs.microsoft.com/en-us/windows/win32/api/winnt/nf-winnt-rtlunwind > > 2 > > > https://docs.microsoft.com/en-us/windows/win32/api/winnt/nf-winnt-rtlunwind > > ex > > > https://docs.microsoft.com/en-us/windows/win32/api/winnt/nf-winnt-r...

...use LLVM/clang to build a binary for ARM Cortex M platforms. > When I build my binary the linker fails to find these libraries. > > ./bin/clang++ -target arm-none-eabi -mcpu=cortex-m4 ./temp.cpp -L > ./lib/ -L ./libexec/ -L ../build3_v7m/lib/ > ld.lld: error: unable to find library -lunwind > ld.lld: error: unable to find library -lc > ld.lld: error: unable to find library -lm > ld.lld: error: unable to find library -lclang_rt.builtins-arm.a > > I am guessing I can borrow libraries such as lc and lm from GCC > arm-none-eabi*, but for clang_rt.builtins-arm.a (which I...

...r libunwind, there's really no use for it in an MSVC setting. All > the unwinding functionality is already built into the operating system, > available via the Rtl*Unwind* functions. > Martin, you mean these functions https://docs.microsoft.com/en-us/windows/win32/api/winnt/nf-winnt-rtlunwind https://docs.microsoft.com/en-us/windows/win32/api/winnt/nf-winnt-rtlunwind2 https://docs.microsoft.com/en-us/windows/win32/api/winnt/nf-winnt-rtlunwindex https://docs.microsoft.com/en-us/windows/win32/api/winnt/nf-winnt-rtlvirtualunwind ? > > For libbacktrace, I guess the _Unwind_Backtrace...