search for: _aeabi

...it should cover all library functions as defined by ARM EABI. Right now it misses some, but the calls to them are not generated by clang. No - in general it should not cover gcc's internal functions. Though it can cover *some* functions which are important. So, in your case we need to include _aeabi* and _sync* functions, yes. -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State University

> I'm using Clang, with arm-none-linux-gnueabi-g++ as a linker. Although > compiler-rt replaced libgcc, we still need other libs such as libc, libm, > etc. It seems libc is calling these missing functions. If you compile libc with gcc, then yes, you might need arbitrary functions from libgcc. -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint

So, you mean I should compile libc with clang and link with compiler-rt too? But how can we expect a user of compiler-rt have a libc compiled in this way? It's a part of gcc's src code... If compiler-rt is a complete lib, it should also cover these functions, right? BTW, if libc is compiled statically, shouldn't itself already contain all functions it need? I just get confused now...

...oup -lcompiler-rt-armv7 -lgcc_eh -lc --end-group" vs. "-lstdc++ -lm --start-group -lgcc -lgcc_eh -lc --end-group" ... tools/gcc-4.6.1-cs/arm-2011.09/bin/../arm-none-linux-gnueabi/libc/thumb2/usr/lib/libm.a(mpa.o): In function `norm': mpa.c:(.text+0xba): undefined reference to `__aeabi_dcmplt' Does clang provide other replacing libs for them which don't depend on those missing functions on libgcc? Or there are some other ways to link? Currently I have to link with both compiler-rt and libgcc with "--allow-multiple-definition" so that libgcc can cover the missin...