Re: WITH_LLVM_LIBUNWIND vs. WITHOUT_LLVM_LIBUNWIND, clang vs. gcc (such as devel/powerpc64-xtoolchain-gcc ): What is intended to be required for C++ exceptions to work?

Quick summaries from looking around at official amd64 builds (via downloaded .iso's installed in VirtualBox under Mac OS X): _Unwind_RaiseException content (amd64 context only): RaiseExc. RaiseExc. RaiseException dwarfdump save/rest. has "mov %rcx,%rsp"

[Bug 214863] lang/gcc + libc++ may fail due to spurious __cxa_throw_bad_array_new_length reference

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214863 --- Comment #9 from Baptiste Daroussin --- well this is a bug :) They should not -- You are receiving this mail because: You are on the CC list for the bug. ___

Re: WITH_LLVM_LIBUNWIND vs. WITHOUT_LLVM_LIBUNWIND, clang vs. gcc (such as devel/powerpc64-xtoolchain-gcc ): What is intended to be required for C++ exceptions to work?

[A top-post noting that it is head -r309179 that is different from 9.3-RELELASE for _Unwind_raiseException --and from stable/11 -r309125-- after noting my repeated "stable/11" references that should have said "head". Also for code that uses libgcc_s.so.1 for C++ exception handling the odd one is