similar to: [LLVMdev] Compiling LibC++ with LLVM on ARM

Hi Renato, On 24 July 2015 at 04:35, Renato Golin <renato.golin at linaro.org> wrote: > Unwind-EHABI.cpp:1000:47: error: expected unqualified-id before string constant > _LIBUNWIND_EXPORT extern "C" _Unwind_Reason_Code GCC seems to be stricter than Clang about the ordering of __attribute__ (from _LIBUNWIND_EXPORT) and 'extern "C"'. You can play around

On 24 July 2015 at 15:00, Tim Northover <t.p.northover at gmail.com> wrote: > GCC seems to be stricter than Clang about the ordering of > __attribute__ (from _LIBUNWIND_EXPORT) and 'extern "C"'. Humpf, that seems to be an old thing. GCC 5.1 on my laptop cope with that just fine. :( thanks! --renato

On 24 July 2015 at 07:51, Renato Golin <renato.golin at linaro.org> wrote: > On 24 July 2015 at 15:00, Tim Northover <t.p.northover at gmail.com> wrote: >> GCC seems to be stricter than Clang about the ordering of >> __attribute__ (from _LIBUNWIND_EXPORT) and 'extern "C"'. > > Humpf, that seems to be an old thing. GCC 5.1 on my laptop cope with

> On 18 Nov 2019, at 22:11, Peter Smith <peter.smith at linaro.org> wrote: > > On Mon, 18 Nov 2019 at 17:06, Sergej Jaskiewicz <jaskiewiczs at icloud.com <mailto:jaskiewiczs at icloud.com>> wrote: >> >> >> >> On 18 Nov 2019, at 19:55, Peter Smith <peter.smith at linaro.org> wrote: >> >> On Mon, 18 Nov 2019 at 15:23, Sergej

On 04/12/2019 06:31 PM, Tom Stellard via llvm-dev wrote: > On 04/12/2019 04:28 PM, AiChi via llvm-dev wrote: >> Hi, >> >> I'm currently working on one of my team's project to build LLVM full clang toolchain (Clang, libcxx, libcxxabi) on a CentOS machine. >> >> Previously we compiled our codebase with llvm-toolset-7/clang++, which by default takes stdlibc++

Hi Marshal, ARM has recently moved the buildslave from single test to with/without exception: http://lab.llvm.org:8011/builders/libcxx-libcxxabi-libunwind-arm-linux http://lab.llvm.org:8011/builders/libcxx-libcxxabi-libunwind-arm-linux-noexceptions but both slaves have the same error that wasn't there before: ******************** TEST 'libc++ ::

Hi, I recently tried to build libcxxabi on ARM/Linux but looks like libunwind is not providing the necessary symbols needed, precisely _Unwind_SjLj_RaiseException and related functions are missing. Did anyone have any success with this before? Thanks, ismail -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi cschen, It seems that libunwind (the one included in libcxxabi) is mandatory at the moment. Use the second build command instead: $ CROSS_COMPILING=arm ENABLE_LIBUNWIND=1 ./scripts/compile-all.sh Logan On Tue, Oct 7, 2014 at 5:32 PM, gamma_chen <gamma_chen at yahoo.com.tw> wrote: > After do "sudo apt-get update", the following are pass. > > Install the

# Everything is done on Mac OS X 10.8.4, with llvm/clang/libc++/libc++abi built from source this morning # totclang is an alias for the built clang. $ export LLVM=/Sources/LLVM $ export LIBCXX=$LLVM/libcxx $ export LIBCXXABI=$LLVM/libcxxabi $ totclang -std=c++11 -stdlib=libc++ -I $LIBCXX/include -fsanitize=undefined ubsan.cpp -L $LIBCXX/lib -L $LIBCXXABI/lib -lc++abi $

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 LIBCXX_HAS_GCC_S_LIB=OFF CLANG_DEFAULT_CXX_STDLIB=libc++ CLANG_DEFAULT_LINKER=lld CLANG_DEFAULT_RTLIB=compiler-rt LLVM_DEFAULT_TARGET_TRIPLE=x86_64-pc-linux-musl LLVM_TARGET_ARCH=x86_64

Hi, I'm currently working on one of my team's project to build LLVM full clang toolchain (Clang, libcxx, libcxxabi) on a CentOS machine. Previously we compiled our codebase with llvm-toolset-7/clang++, which by default takes stdlibc++ to compile and link. And now we'd like to switch to use LLVM clang with libc++. I have built libc++ and libc++abi from source (5.0.1 release) and set

On Fri, Jan 30, 2015 at 12:37 PM, Nick Kledzik <kledzik at apple.com> wrote: > I thought the ARM EHABI added a twist to this because it created some > upward dependency from the unwinder to libc++abi. > > Other than that, I don’t have any strong feeling where it lives. > +1 to this. If you don't break the EHABI unwinder while moving things around, I'm happy. +Dan,

Thanks Shoaib for a great summary. To summarize this as an answer to Louis' questions: 1. What is a "Standalone build"? What does it enable that a normal monorepo build can't? This means building any of the runtimes separately, where the runtime's CMakeLists.txt (e.g. path/to/my/llvm-project/libcxx/CMakeLists.txt) is the top-level one. The reason for using this variant is

Hi cschen, Here are the test scripts which I written when I was developing ARM exception handling support: https://github.com/loganchien/libcxx-scripts The script should work on Debian wheezy (cross-compiling from amd64 to armhf.) In general, here are the necessary steps: 1. Get a working arm-linux-gnueabihf gcc/g++ toolchain (for the headers and libraries) 2. Setup the include search path

I thought the ARM EHABI added a twist to this because it created some upward dependency from the unwinder to libc++abi. Other than that, I don’t have any strong feeling where it lives. -Nick On Jan 30, 2015, at 12:33 PM, Renato Golin <renato.golin at linaro.org> wrote: > On 30 January 2015 at 20:17, Saleem Abdulrasool <compnerd at compnerd.org> wrote: >> There is a valid

Hello, lately, I have been thinking about how to resolve the problem with that the program size increases enormously when including <iostream> when compiling with libstdc++. In this library, in <iostream> there is a static object __ioinit initialized like so: ... // For construction of filebuffers for cout, cin, cerr, clog et. al. static ios_base::Init __ioinit; ... This

[Cross-post to llvm-dev to make sure everybody relevant sees this] Hi, I'm currently trying to simplify the libc++/libc++abi/libunwind build systems and testing setup. In doing so, I am encountering issues related to "unusual" ways of building them. By unusual, I just mean "not the usual monorepo build with LLVM_ENABLE_PROJECTS". I would like to pin down what the set of

On 15 March 2014 17:06, Logan Chien <tzuhsiang.chien at gmail.com> wrote: > I would like to know what do you mean by "commoning them up"? Hi Logan, That'd be reducing ARM directives in favour of CFI, but as I said (and you too), GNU compatibility will probably be an issue for a very long time. > For the space issue, I personally don't think this is a big issue.

Hi Ioannis, Just delete the projects/libcxx directory, then rebuild from scratch. You should only need to checkout llvm (in the top level directory) and cfe (into the tools/clang subdirectory). -Dimitry > On 29 Mar 2016, at 00:08, Ioannis Koukoulis <i.g.koukoulis at gmail.com> wrote: > > Hi Dimitry, > > I do not particularly need to build libc++ from the package. Is the

Hi Dimitry, this definitely worked. I am passed by the linking errors regarding libc++ or similar. My build stopped now at 95% while linking a clang extra, I am not pretty sure which because i do not have my laptop, possible the clang-rename, if such exists. No undefined references here, however, my hdd's free space run out, so this might be the cause. I have to move or expand now, alas!! The