similar to: [LLVMdev] How to disable or override libgcc when linking?

Hi, I'm trying to link my objs with compiler-rt built runtime lib for arm. According to the compiler-rt doc, it should be able to replace libgcc. However, if I replace "-lgcc" with "compiler-rt.a" for a static linking, gcc linker complains about undefined functions. Using "nm -g", I compared the functions in libgcc and compiler-rt.full-arm.a and found there are

On Nov 15, 2012, at 9:33 PM, liangh at codeaurora.org wrote: > I'm trying to link my objs with compiler-rt built runtime lib for arm. > According to the compiler-rt doc, it should be able to replace libgcc. > However, if I replace "-lgcc" with "compiler-rt.a" for a static linking, > gcc linker complains about undefined functions. Using "nm -g", I

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. > > On Nov 15, 2012, at 9:33 PM, liangh at codeaurora.org wrote: >> I'm trying to link my objs with compiler-rt built runtime lib for arm. >> According to the compiler-rt

Nick, How exactly do you envision this being done? Looking at the contents of config/darwin.h, I see... /* Support -mmacosx-version-min by supplying different (stub) libgcc_s.dylib libraries to link against, and by not linking against libgcc_s on earlier-than-10.3.9. Note that by default, -lgcc_eh is not linked against! This is because in a future version of Darwin the EH frame

1 hour ago I downloaded llvm-3.6.0-rc4-win32.exe from http://llvm.org/pre-releases/3.6.0/ . I tried to compile simple C code that just print "hello" , but it didn't compile , because clang.exe can't find . when I use clang-cl.exe with the same code , it worked . I also have the same problem with clang++ even with , I add -I flag to GCC (4.9.1) C++ headers , the result:

We develop software and are beginning a slow transition from 32 bit applications to their 64 bit equivalents. During this period it will be necessary to build programs targeted for both environments using the x86-64 machines for development. here is a simple/small "application", sizes.c: #include <stdio.h> #include <stdlib.h> int main(int argc, char **argv) {

Sorry for not explaining well. After compiling with g++-cross g++-cross -c a.c I do link using this command /gold_binutils/build/gold/ld-new -plugin ~/Desktop/Sanjeev/LLVM/llvm-2.7/Release/lib/libLLVMgold.so --eh-frame-hdr -melf_i386 -dynamic-linker /lib/ld-linux.so.2 /usr/lib/crt1.o /usr/lib/crti.o /usr/local/lib/gcc/i686-pc-linux-gnu/4.2.0/crtbegin.o

Hi, I am trying to compile R-2.2.1 on Solaris 2.9 with a 64-bit build. Following the instructions in "R Installation and Adminstration", I changed the following settings in "config.site": CC="gcc -m64" F77="g77 -64" CXX="g++ -m64" LDFLAGS="-L/usr/local/lib/sparcv9 -L/usr/local/lib" But I got the following error messages:

I am new to LLVM. I am using Clang 3.0 to execute c programs. I am using mandriva spring 2010. GCC version 4.4.1 is installed in the system. I used the following link to install LLVM. svn co http://llvm.org/svn/llvm-project/llvm/trunk llvm I run it by using the below command clang file.c. I am getting the following error. /usr/bin/ld: cannot find -lgcc clang: error: linker command failed with

> ~/Desktop/Sanjeev/LLVM/llvm-2.7/Release/lib/libLLVMgold.so --eh-frame-hdr > -melf_i386 -dynamic-linker /lib/ld-linux.so.2 /usr/lib/crt1.o Ok, this way you're generating code for x86 > /usr/lib/crti.o > /usr/local/lib/gcc/i686-pc-linux-gnu/4.2.0/crtbegin.o > -L/usr/local/lib/gcc/i686-pc-linux-gnu/4.2.0  -L/usr/local/lib -lgcc > --as-needed -lgcc_s --no-as-needed -lc -lgcc

This may be that the libgcc_s.dylib based unwinder is incompatible with the darwin unwinder. You cannot mix and match the two. One of the lines from the bugzilla comments shows: /sw/lib/gcc4.5/lib/libgcc_s.1.dylib (compatibility version 1.0.0, being used. That will not work. All of the libgcc_s.dylib functionality has been subsumed into libSystem.dylib on SnowLeopard (darwin10). The

I realize this is off-topic for the list, but I thought all the darwin developers here might want to be aware of this. The current regressions in gcc trunk regarding exception handling has been escalated to a P1 in order to attract darwin developers to the issue... http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41260#c31 If these regressions aren't fixed before gcc 4.5's release, it appears

hi, Dale Johannesen wrote: > On Oct 19, 2007, at 7:23 AM, Dietmar Ebner wrote: >> i'm trying to make some experiments with the ARM backend (llvm 2.1) >> and >> therefore built an arm-softfloat-linux-gnu toolchain on x86_64 linux. >> >> however, the llvm-gcc frontend seems to cause troubles with single >> precision floating point values, i.e., they are

Hello all, I have been tasked with "fixing" one of our CentOS boxes by somehow downgrading the libgcc and gcc packages to a specific version (Required by the Oracle Grid Control client). Normally I'd just remove and reinstall the packages however removing libgcc is no fun as I found out the hard way it breaks pretty much every package including rpm & yum. Is there an elegant way

Alpine linux is a distribution that uses musl libc instead glibc. Here are my steps to reproduce: On Alpine linux, download LLVM, Clang, LLD 6.0.0 from releases.llvm.org, and build them from source. $ clang -c hello_world.c $ ld.lld --gc-sections -m elf_x86_64 -o hello_world /usr/lib/gcc/x86_64-alpine-linux-musl/6.4.0/../../../../lib/Scrt1.o

Hi llvmdev! I've been working on implementing support for segmented stacks in LLVM (towards GSoC '11). Currently I'm working on adding intrinsics for coroutines. The problem is this: Till now I had been depending on libgcc for runtime support (and was being 100% libgcc compatible in the process). However, since all the stack allocation routines in libgcc depend on TLS variables to

Hi, both https://git.kernel.org/pub/scm/libs/klibc/klibc.git/plain/usr/klibc/arch/i386/libgcc/__ashldi3.S and https://git.kernel.org/pub/scm/libs/klibc/klibc.git/plain/usr/klibc/arch/i386/libgcc/__lshrdi3.S use the following code sequences for shift counts greater 31: 1: 1: xorl %edx,%edx shrl %cl,%edx shl %cl,%eax xorl %eax,%eax

Hi guys, Thanks for all the info. Then, if, besides compiler-rt, I also need some other libs, such as libm, how do I link? Here is an example of missing functions in compiler-rt when linking: "-lstdc++ -lm --start-group -lcompiler-rt-armv7 -lgcc_eh -lc --end-group" vs. "-lstdc++ -lm --start-group -lgcc -lgcc_eh -lc --end-group" ...

Hello It seems you misses several points here... > 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... No it is not > If compiler-rt is a complete lib, it should also cover these functions, right? Yes and no. Yes - it should cover all