search for: gcc_personality_v0

In lib/gcc_personality_v0.c, I believe the type of the exception_cleanup member of the struct _Unwind_Exception is incorrect. It has a return type of _Unwind_Reason_Code versus a return type of void as specified in http://refspecs.freestandards.org/abi-eh-1.21.html, and as can be seen in unwind.h on Linux, and OS X 10.6....

...3:50: note: expanded from macro '__cleanup_fct_attribute' # define __cleanup_fct_attribute __attribute__ ((__regparm__ (1))) ^ ~ 3 errors generated. [148/207] Building C object lib/builtins/CMakeFiles/clang_rt.builtins-armhf.dir/gcc_personality_v0.c.o /home/llvm_all/llvm/projects/compiler-rt/lib/builtins/gcc_personality_v0.c:148:47: warning: declaration of 'struct _Unwind_Exception' will not be visible outside of this function [-Wvisibility] _Unwind_Reason_Code __gnu_unwind_frame(struct _Unwind_Exception *,...

...39;__cleanup_fct_attribute' >> # define __cleanup_fct_attribute __attribute__ ((__regparm__ (1))) >> ^ ~ >> 3 errors generated. >> [148/207] Building C object lib/builtins/CMakeFiles/clang_rt.builtins-armhf.dir/gcc_personality_v0.c.o >> /home/llvm_all/llvm/projects/compiler-rt/lib/builtins/gcc_personality_v0.c:148:47: warning: declaration of 'struct _Unwind_Exception' will not be visible outside of this function [-Wvisibility] >> _Unwind_Reason_Code __gnu_unwind_frame(struct _Unwind_Exception *, >>...

...__cleanup_fct_attribute' > > # define __cleanup_fct_attribute __attribute__ ((__regparm__ (1))) > > ^ ~ > > 3 errors generated. > > [148/207] Building C object lib/builtins/CMakeFiles/clang_rt.builtins-armhf.dir/gcc_personality_v0.c.o > > /home/llvm_all/llvm/projects/compiler-rt/lib/builtins/gcc_personality_v0.c:148:47: warning: declaration of 'struct _Unwind_Exception' will not be visible outside of this function [-Wvisibility] > > _Unwind_Reason_Code __gnu_unwind_frame(struct _Unwind_Exception *, > &...

Clang does indeed built it with one warning. [ 55%] Building C object lib/CMakeFiles/CompilerRT-Common.dir/gcc_personality_v0.c.o /export/home/edward/lab/llvm/build/compiler-rt/lib/gcc_personality_v0.c:232:36: warning: implicit declaration of function '__builtin_eh_return_data_regno' is invalid in C99 [-Wimplicit-function-declaration] _Unwind_SetGR(context, __builtin_eh_return_data_regno(0),...

...>>> # define __cleanup_fct_attribute __attribute__ ((__regparm__ (1))) > >>> ^ ~ > >>> 3 errors generated. > >>> [148/207] Building C object lib/builtins/CMakeFiles/clang_rt.builtins-armhf.dir/gcc_personality_v0.c.o > >>> /home/llvm_all/llvm/projects/compiler-rt/lib/builtins/gcc_personality_v0.c:148:47: warning: declaration of 'struct _Unwind_Exception' will not be visible outside of this function [-Wvisibility] > >>> _Unwind_Reason_Code __gnu_unwind_frame(struct _Unwind_Exc...

...ed from macro '__cleanup_fct_attribute' > # define __cleanup_fct_attribute __attribute__ ((__regparm__ (1))) > ^ ~ > 3 errors generated. > [148/207] Building C object lib/builtins/CMakeFiles/clang_rt.builtins-armhf.dir/gcc_personality_v0.c.o > /home/llvm_all/llvm/projects/compiler-rt/lib/builtins/gcc_personality_v0.c:148:47: warning: declaration of 'struct _Unwind_Exception' will not be visible outside of this function [-Wvisibility] > _Unwind_Reason_Code __gnu_unwind_frame(struct _Unwind_Exception *, >...

...ed from macro '__cleanup_fct_attribute' > # define __cleanup_fct_attribute __attribute__ ((__regparm__ (1))) > ^ ~ > 3 errors generated. > [148/207] Building C object lib/builtins/CMakeFiles/clang_rt.builtins-armhf.dir/gcc_personality_v0.c.o > /home/llvm_all/llvm/projects/compiler-rt/lib/builtins/gcc_personality_v0.c:148:47: warning: declaration of 'struct _Unwind_Exception' will not be visible outside of this function [-Wvisibility] > _Unwind_Reason_Code __gnu_unwind_frame(struct _Unwind_Exception *, >...

...pported mechanisms are found. I'll look at that. Thanks for the feedback! Shantonu Sent from my MacBook On Sep 22, 2009, at 9:01 PM, Edward O'Callaghan wrote: > Clang does indeed built it with one warning. > > [ 55%] Building C object > lib/CMakeFiles/CompilerRT-Common.dir/gcc_personality_v0.c.o > /export/home/edward/lab/llvm/build/compiler-rt/lib/ > gcc_personality_v0.c:232:36: > warning: implicit declaration of function > '__builtin_eh_return_data_regno' is invalid in C99 > [-Wimplicit-function-declaration] > _Unwind_SetGR(context, __builtin...

...ds on it for EHABI calls, which is defined by default on ARM environments. The end result is that I can only use Clang 3.9+ to compile libunwind 3.9+. http://buildmaster.tcwglab.linaro.org/builders/clang-cmake-armv7-a15-full/builds/1788/steps/build%20stage%201/logs/stdio compiler-rt/lib/builtins/gcc_personality_v0.c:149:57: error: use of undeclared identifier '_URC_OK'; did you mean '_UVRSR_OK'? if (__gnu_unwind_frame(exceptionObject, context) != _URC_OK) ^~~~~~~ Do we take this as an ABI break and document it? Or do we try to fix i...

Seems pretty clear cut to me. #if defined(HAVE_OSATOMIC_COMPARE_AND_SWAP_INT) && defined (HAVE_OSATOMIC_COMPARE_AND_SWAP_LONG) ... #elif defined(__WIN32__) ... #elif defined(HAVE_SYNC_BOOL_COMPARE_AND_SWAP_INT) && defined (HAVE_SYNC_BOOL_COMPARE_AND_SWAP_LONG) ... #else #error unknown atomic compare-and-swap primitive #endif The problem isn't mismatched #if/#endif. The

...BI info - done -- Detecting CXX compile features -- Detecting CXX compile features - done -- Looking for unwind.h -- Looking for unwind.h - found -- Found PythonInterp: /usr/bin/python2.7 (found version "2.7.15") -- Looking for fopen in c -- Looking for fopen in c - found -- Looking for __gcc_personality_v0 in gcc_s -- Looking for __gcc_personality_v0 in gcc_s - found -- Performing Test COMPILER_RT_HAS_NODEFAULTLIBS_FLAG -- Performing Test COMPILER_RT_HAS_NODEFAULTLIBS_FLAG - Success -- Performing Test COMPILER_RT_HAS_FFREESTANDING_FLAG -- Performing Test COMPILER_RT_HAS_FFREESTANDING_FLAG - Success -...

No, As it worked fine before. I can't see the #if that goes with +#elif defined(__WIN32__) as you removed -#if TARGET_OS_MAC. Please go over your #if / #endif blocks and trail the #endif with a comment. I am willing to bet there is a problem there. Thanks for your time, Edward. 2009/9/23 Shantonu Sen <ssen at apple.com>: > Sounds like your system compiler doesn't support

>Exceptions >All eh pads are grouped together regardless of their coldness and are part of the original function. There are outstanding issues with splitting eh pads if they reside in separate sections in the binary. This remains as part of future work. Can you elaborate more on the outstanding issues with splitting eh pads? From my dip into the unwind map in gcc_except_table the