similar to: Cross-compiling libc++ to linux-armv7hf gives undefined symbols in cmath / math.h

At first glance, it looks like long double functions (such as fabsl and friends) are missing from your sysroot's <math.h>. Does your target support long double at all? -Dimitry > On 6 Feb 2018, at 09:51, Tobias Hieta via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Hello, > > I am trying to cross-compile libc++ from my x86_64 linux system to armv7hf. We have

Hello Dimitry and thanks for your answer. I am pretty sure it does indeed support long double. It's configured with vfpv3-d16 - but I noticed that c++config.h in gcc has _GLIBCXX__HAS_FABSL and friends are undefined. I think I need to look deeper at the configuration of our toolchain. long double support is required in libc++ then I gather? -- Tobias On Tue, Feb 6, 2018 at 11:47 AM,

Hello, I am trying to cross-compile libc++ from my x86_64 linux system to armv7hf. We have our own gcc compiler that we build with crosstools-ng (based on gcc 6.3.0) and I set my environment like this: CC=armv7a-plex-linux-gnueabihf-gcc CXX=armv7a-plex-linux-gnueabihf-g++ CFLAGS=-fPIC -DPIC -mfloat-abi=hard -march=armv7-a -Os -mfpu=vfpv3-d16 --sysroot=<path> CXXFLAGS=-fPIC -DPIC

cmake -E cmake_progress_report llvm-3.8.0.src_bld_x86_64-rhel6.4-linux-gnu/CMakeFiles In file included from llvm-3.8.0.src/projects/libcxx/include/__hash_table:19:0, from llvm-3.8.0.src/projects/libcxx/src/hash.cpp:10: llvm-3.8.0.src/projects/libcxx/include/cmath:310:9: error: '::signbit' has not been declared using ::signbit; ^

Greetings! I have been building llvm-3.6.x, 3.7.1 and 3.7.2 with (glibc-2.12.1, binutils-2.24, gcc-4.9.2) almost same set if CMake flags. However while building LLVM-3.8.0 using same CMake flags I am observing projects/libcxx/include/cmath errors... ...'::signbit' has not been declared ...'::fpclassify' has not been declared ...'::isfinite' has not been declared ...

Hi, I am observing a strange behaviour in which Clang ignores __restirct when I include some standard headers. For example, this code: void vec_add(int* __restrict a, int* __restrict b, int n) { #pragma unroll 4 for(int i=0; i<n; ++i) { a[i] += b[i]; } } results in: ; Function Attrs: nofree norecurse nounwind define dso_local void @_Z7vec_addPiS_i(i32*

Hello, Recently we tried to streamline our toolchain by removing some GNU tools with LLVM tools to avoid having multiple copies of strip, nm, ar and similar tools. Today we ran into a really strange issue where shared objects where not loadable. We where able to track this down to llvm-strip with default arguments creating a shared object that doesn't load correctly. It works if we switch

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

*System:* Debian Linux Sid/Unstable amd64 *LLVM/Clang:* Trunk *Scenario:* In the past couple of days I've been compiling against trunk I get two separate and spurious hang ups with CMake. *Note:* I build against more than just X86 follow along the progress of other platforms, though just building for X86 produces the same results below. *Assumption:* Configure cmake with prior built

Hello Rui, Thanks for your reply. I tried with the keep-section argument and that made the shared library work. Should these sections be kept around by default maybe? -- Tobias On Thu, Oct 17, 2019 at 11:06 AM Rui Ueyama <ruiu at google.com> wrote: > > One thing I noticed is that llvm-strip seemed to remove a .ARM.attributes section. Can you try --keep-section=.ARM.attributes to

Hi Brian, I've been playing around with your test programs and came to the result: --------------------- #ifdef __INTERIX # define _GLIBCPP_USE_C99 1 //Define this macro before including isnan() function from cmath #endif #include <cmath> using std::isnan; int foo(float f) {return isnan(f);} --------------------- /Henrik >From: "Brian R. Gaeke" <gaeke at

Hello Tobias, I think that looks reasonable to me, I think it will be down to the llvm-objcopy team whether they want to make .ARM.attributes a special case or not. The best way to find out is to submit a patch, citing the problems with old versions of libc, I'd expect that you'll need to add a test case for the patch to be accepted. To do that it is probably best to look at the existing

when i try to install openh323gk i get the following error please help ldaplink.cxx:345: call of overloaded `pow(double, unsigned int&)' is ambiguous /usr/include/bits/mathcalls.h:143: candidates are: double pow(double, double) /usr/include/g++/cmath:427: long double std::pow(long double, int) /usr/include/g++/cmath:423: float std::pow(float, int)

Jordan, I have sent the patch via Phabricator: https://reviews.llvm.org/D69188 Let me know if I got it right. -- Tobias On Thu, Oct 17, 2019 at 7:12 PM Jordan Rupprecht <rupprecht at google.com> wrote: > > Tobias, > I don't have much experience with ARM, but from your report and Peter's explanation of why LLD does it, I agree we should be consistent with LLD and keep the

Hello everyone, Below are some buildbot numbers for the week of 2/25/2018 - 3/03/2018. Please see the same data in attached csv files: The longest time each builder was red during the week; "Status change ratio" by active builder (percent of builds that changed the builder status from greed to red or from red to green); Count of commits by project; Number of completed builds, failed

Hello everyone, Below are some buildbot numbers for the last week of 3/18/2018 - 3/24/2018. Please see the same data in attached csv files: The longest time each builder was red during the week; "Status change ratio" by active builder (percent of builds that changed the builder status from greed to red or from red to green); Count of commits by project; Number of completed builds,

Hello everyone, Below are some buildbot numbers for the week of 5/6/2018 - 5/12/2018. Please see the same data in attached csv files: The longest time each builder was red during the week; "Status change ratio" by active builder (percent of builds that changed the builder status from greed to red or from red to green); Count of commits by project; Number of completed builds, failed

Hello everyone, Below are some buildbot numbers for the week of 1/21/2018 - 1/27/2018. Please see the same data in attached csv files: The longest time each builder was red during the week; "Status change ratio" by active builder (percent of builds that changed the builder status from greed to red or from red to green); Count of commits by project; Number of completed builds, failed

Hello everyone, Below are some buildbot numbers for the week of 4/8/2018 - 4/14/2018. Please see the same data in attached csv files: The longest time each builder was red during the week; "Status change ratio" by active builder (percent of builds that changed the builder status from greed to red or from red to green); Count of commits by project; Number of completed builds, failed

Hello everyone, Below are some buildbot numbers for the last week of 4/29/2018 - 5/5/2018. Please see the same data in attached csv files: The longest time each builder was red during the week; "Status change ratio" by active builder (percent of builds that changed the builder status from greed to red or from red to green); Count of commits by project; Number of completed builds,