search for: lgcc_eh

...incompatible /work/net-local-b/sparc- sun-solaris2.9/bin/../lib/gcc/sparc-sun-solaris2.9/3.4.2/sparcv9/libgcc.a when search ing for -lgcc /usr/ccs/bin/ld: skipping incompatible /work/net-local-b/sparc- sun-solaris2.9/bin/../lib/gcc/sparc-sun-solaris2.9/3.4.2/sparcv9/libgcc_eh.a when sea rching for -lgcc_eh /usr/ccs/bin/ld: skipping incompatible /lib/sparcv9/libc.so when searching for -lc /usr/ccs/bin/ld: skipping incompatible /usr/lib/sparcv9/libc.so when searching for -lc /usr/ccs/bin/ld: skipping incompatible /usr/lib/sparcv9/libc.so when searching for -lc /usr/ccs/bin/ld: skipping incompatible /wo...

...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 information may be in a new format, or the fallback routine might be changed; if you want to explicitly link against the static version of those routines, because you know you don't need to unwind thr...

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" ... 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 pr...

...\CIndex.cpp.obj ..\..\..\..\lib\libLLVMMC.a ..\..\..\..\lib\libLLVMSupport.a ..\..\..\..\lib\libLLVMSystem.a ..\..\..\..\lib\libclangFrontend.a ..\..\..\..\lib\libclangIndex.a ..\..\..\..\lib\libclangSema.a ..\..\..\..\lib\libclangAST.a ..\..\..\..\lib\libclangLex.a ..\..\..\..\lib\libclangBasic.a -lgcc_eh -lgcc_eh -lkernel32 -luser32 -lgdi32 -lwinspool -lshell32 -lole32 -loleaut32 -luuid -lcomdlg32 -ladvapi32 ..\..\..\..\lib\libclangFrontend.a(ASTUnit.cpp.obj):ASTUnit.cpp:(.text$_ZN5clang13SourceManagerC1Ev[clang::SourceManager::SourceManager()]+0xf): undefined reference to `llvm::BumpPtrAllocator::...

...-lm -lgcc_s -lfrtbegin: - lg2c: checking how to get verbose linking output from gcc... -v checking for C libraries of gcc... -L/usr/ccs/lib -L/usr/lib - L/usr/local/lib -L/usr/local/lib/gcc-lib/i386-pc-solaris2.10/3.3.2 - L/usr/ccs/bin -L/usr/local/lib/gcc-lib/i386-pc- solaris2.10/3.3.2/../../.. -lgcc_eh checking for dummy main to link with Fortran libraries... unknown configure: error: linking to Fortran libraries from C fails See `config.log' for more details. I have installed gcc from sunfreeware Looks like the following are not found:- configure:26575: gcc -o conftest -g -O2 -I/usr/loca...

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

On Sun, Jul 22, 2012 at 11:12 PM, Renato Golin <rengolin at systemcall.org> wrote: > On 22 July 2012 22:03, salvatore benedetto > <salvatore.benedetto at gmail.com> wrote: >> While we are at it, if a new comer would like to understand where everything >> takes place, where should he look? >> >> I did a grep in the source and eventually ended up in

On 22 July 2012 22:03, salvatore benedetto <salvatore.benedetto at gmail.com> wrote: > While we are at it, if a new comer would like to understand where everything > takes place, where should he look? > > I did a grep in the source and eventually ended up in clang/something/driver. That's pretty much it: clang/lib/Driver

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

...one? 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 information may > be in a new format, or the fallback routine might be changed; if > you want to explicitly link against the static version of those > routines, because you know you don't ne...

...lang --target arm-none-linux-gnueabi -nostdlib -static hello.c ~/research/musl-1.1.6/lib/crt1.o ~/research/musl-1.1.6/lib/crti.o ~/research/musl-1.1.6/lib/crtn.o -I ~/research/musl-1.1.6/include/ -L ~/research/musl-1.1.6/lib/ -L /usr/local/arm-2009q3/lib/gcc/arm-none-linux-gnueabi/4.4.1/ -lc -lgcc -lgcc_eh clang complaint: /usr/local/arm-2009q3/bin/arm-none-linux-gnueabi-ld: warning: library search path "/lib/../lib" is unsafe for cross-compilation /usr/local/arm-2009q3/bin/arm-none-linux-gnueabi-ld: warning: library search path "/usr/lib/../lib" is unsafe for cross-compilation...

...sr/lib/../lib64 -L/opt/gcc/4.7.2/snos/lib/gcc/x86_64-suse-linux/4.7.2/../../.. -lrca -L/opt/cray/atp/1.6.2/lib/ -lAtpSigHCommData -lAtpSigHandler -lgfortran -lscicpp_gnu -lsci_gnu_mp -lstdc++ -lmpich_gnu_47 -lmpl -lrt -lxpmem -ldmapp -lugni -lpmi -lalpslli -lalpsutil -ludreg -lpthread -lm -lgomp -lgcc_eh checking for dummy main to link with Fortran 77 libraries... none checking for Fortran 77 name-mangling scheme... lower case, underscore, no extra underscore checking whether ftn appends underscores to external names... yes checking whether ftn appends extra underscores to external names... no chec...

I followed the build instructions for LLVM+clang -- that all went OK. But compiling a simple "hello world" program with clang++ gives a linker error -- see attached log file. - Paul -------------- next part -------------- A non-text attachment was scrubbed... Name: build.log Type: application/octet-stream Size: 1881 bytes Desc: not available URL:

...fmudflap|fmudflapth: --wrap=malloc --wrap=free --wrap=calloc --wrap=realloc --wrap=mmap --wrap=munmap --wrap=alloca} %{fmudflapth: --wrap=pthread_create}} %{fmudflap|fmudflapth: --wrap=main} *mflib: %{fmudflap|fmudflapth: -export-dynamic} *link_gomp: *libgcc: %{static|static-libgcc:-lgcc -lgcc_eh}%{!static:%{!static-libgcc:%{!shared-libgcc:-lgcc --as-needed -lgcc_s --no-as-needed}%{shared-libgcc:-lgcc_s%{!shared: -lgcc}}}} *startfile: %{!shared: %{pg|p|profile:gcrt1.o%s;pie:Scrt1.o%s;:crt1.o%s}} crti.o%s %{static:crtbeginT.o%s;shared|pie:crtbeginS.o%s;:crtbegin.o%s} *switches_need_s...

> > FWIW, I build baremetal newlib for arm-eabi using clang, and it works. I >> had to patch a few of the __attribute__((naked)) functions because they >> were using pre-UAL asm syntax, but for the most part it "just works". >> > I build the baremetal newlib using arm-none-eabi-gcc as well, but after linking with the hello world program, it failed to run on

...cal/lib -L/dska/local/bin/../lib/gcc-lib/i386-pc-solaris2.10/3.3.6 -L/dska/local/bin/../lib/gcc-lib -L/usr/local/lib/gcc-lib/i386-pc-solaris2.10/3.3.6 -L/usr/ccs/bin -L/dska/local/bin/../lib/gcc-lib/i386-pc-solaris2.10/3.3.6/../../.. -L/usr/local/lib/gcc-lib/i386-pc-solaris2.10/3.3.6/../../.. -lgcc_eh checking for dummy main to link with Fortran libraries... none checking for Fortran name-mangling scheme... lower case, underscore, extra underscore checking whether g77 appends underscores to external names... yes checking whether mixed C/Fortran code can be run... yes checking whether g77 and gc...