search for: __cxa_allocate_exception

...} 5 %struct.__type_info_pseudo = type { i8*, i8* } 6 @_ZTIi = external constant %struct.__fundamental_type_info_pseudo ; <%struct.__fundamental_type_info_pseudo*> [#uses=1] 7 8 define i32 @main() { 9 entry: 10 %0 = tail call i8* @__cxa_allocate_exception(i32 4) nounwind ; <i8*> [#uses=2] 11 %1 = bitcast i8* %0 to i32* ; <i32*> [#uses=1] 12 store i32 34, i32* %1, align 4 13 invoke void @__cxa_throw(i8* %0, i8* bitcast (%struct.__fundamental_type_info_pseudo* @_ZTIi to i8*), vo...

..."e-p:64:64:64-i1:8:8-i8:8:8-i16:16:16-i32:32:32-i64:64:64-f32:32:32-f64:64:64-v64:64:64-v128:128:128-a0:0:64-s0:64:64-f80:128:128-n8:16:32:64-S128" target triple = "x86_64-unknown-linux-gnu" @_ZTIi = external constant i8* define void @_Z8throwIntv() uwtable { %1 = call i8* @__cxa_allocate_exception(i64 4) nounwind %2 = bitcast i8* %1 to i32* store i32 1, i32* %2 call void @__cxa_throw(i8* %1, i8* bitcast (i8** @_ZTIi to i8*), i8* null) noreturn unreachable ; No predecessors! ret void } declare i8* @__cxa_allocate_exception(i64) dec...

...cussion, but I have to admit, that my skills aren't high enough to follow you guys. For my current exception problem, I don't have to stick around with the PECOFF format, so I used clang to don't compile to a PECOFF, but to a ELF file. Interesting, now I'm missing the functions: __cxa_allocate_exception __cxa_throw _ZTI I loaded the DLL "libstdc++.dll" and found all of the addresses - but the application still crashes when the exception is thrown. So... Do you think, that "Julias Code" could help me? You mentioned her in one of the mails, but I don't know her - or her c...

...ailures on various platforms, e.g. PR24222. We never ran these tests in previous releases, so it's not a regression. It would be great if the sanitizer folks could look into the test failures, but it's not blocking 3.7. - PR24273: "[ARM] Libc++abi built in-tree with libunwind fails in __cxa_allocate_exception", Renato will exclude libc++ from his build for now. - Lack of key functions in some Instruction classes causing build failures without -fno-rtti (http://lists.llvm.org/pipermail/llvm-dev/2015-August/089010.html). No patches have been forthcoming, so this will not get fixed for 3.7. At least...

...gt; CLANG_DEFAULT_LINKER=lld >> CLANG_DEFAULT_RTLIB=compiler-rt >> LLVM_DEFAULT_TARGET_TRIPLE=x86_64-pc-linux-musl >> LLVM_TARGET_ARCH=x86_64 >> LLVM_TARGETS_TO_BUILD=X86 >> >> When linking libc++.so there are a lot of undefined references to __cxa_allocate_exception, __cxa_begin_catch, __cxa_end_catch, __cxa_free_exception, __cxa_guard_abort, __cxa_guard_acquire, __cxa_guard_release, __cxa_pure_virtual, __cxa_rethrow, __cxa_throw, __gxx_personality_v0, _Unwind_Resume, vtable for __cxxabiv1::__class_type_info, vtable for __cxxabiv1::__si_class_type_info, vtable...

...ccAMeZbg.s:111:non-relocatable subtraction expression, "___gxx_personality_v0" minus "L0" ccAMeZbg.s:111:symbol: "___gxx_personality_v0" can't be undefined in a subtraction expression for this reduced testcase: namespace __cxxabiv1 { extern "C" void *__cxa_allocate_exception() throw(); } int bork(void); namespace __gnu_cxx { inline void __throw_concurrence_unlock_error() { } struct __mutex { void unlock() { if (bork() != 0) __throw_concurrence_unlock_error(); } }; } __gnu_cxx::__mutex emergency_mutex; extern "C" void *__cxxa...

On 8/24/07, Chris Lattner <sabre at nondot.org> wrote: > > so how about turning it on? > > It sounds good, but I'm concerned about darwin/x86. Bill, can you see how > well darwin/x86 is doing these days? If there are no regressions from > turning this on by default, we should do it. :) > I'm assuming that this is 4.2? :-) I'll give it a try. -bw

...S_GCC_S_LIB=OFF CLANG_DEFAULT_CXX_STDLIB=libc++ CLANG_DEFAULT_LINKER=lld CLANG_DEFAULT_RTLIB=compiler-rt LLVM_DEFAULT_TARGET_TRIPLE=x86_64-pc-linux-musl LLVM_TARGET_ARCH=x86_64 LLVM_TARGETS_TO_BUILD=X86 When linking libc++.so there are a lot of undefined references to __cxa_allocate_exception, __cxa_begin_catch, __cxa_end_catch, __cxa_free_exception, __cxa_guard_abort, __cxa_guard_acquire, __cxa_guard_release, __cxa_pure_virtual, __cxa_rethrow, __cxa_throw, __gxx_personality_v0, _Unwind_Resume, vtable for __cxxabiv1::__class_type_info, vtable for __cxxabiv1::__si_class_type_info, vtable...

...ren't > > high enough to follow you guys. For my current exception problem, I don't > > have to stick around with the PECOFF format, so I used clang to don't > > compile to a PECOFF, but to a ELF file. Interesting, now I'm missing the > > functions: > > __cxa_allocate_exception > > __cxa_throw > > _ZTI > > > > I loaded the DLL "libstdc++.dll" and found all of the addresses - but the > > application still crashes when the exception is thrown. > > > > So... Do you think, that "Julias Code" could help me? You ment...

On 01/13/2010 02:07 AM, Duncan Sands wrote: > Hi Dustin, the code generators do not support unwind, only the > interpreter does. Ah, the secret is not to even try to frob the gnorts. Manual unwinding, here I come. :-( I was going to say the interpreter doesn't either, but then I recalled it JITs when it can. I don't know how to call into libc from the interpreter to test that.

...gt; ran these tests in previous releases, so it's not a regression. It > > would be great if the sanitizer folks could look into the test > > failures, but it's not blocking 3.7. > > > > - PR24273: "[ARM] Libc++abi built in-tree with libunwind fails in > > __cxa_allocate_exception", Renato will exclude libc++ from his build > > for now. > > > > - Lack of key functions in some Instruction classes causing build > > failures without -fno-rtti > > (http://lists.llvm.org/pipermail/llvm-dev/2015-August/089010.html). No > > patches have been...

...in previous releases, so it's not a regression. It >> > would be great if the sanitizer folks could look into the test >> > failures, but it's not blocking 3.7. >> > >> > - PR24273: "[ARM] Libc++abi built in-tree with libunwind fails in >> > __cxa_allocate_exception", Renato will exclude libc++ from his build >> > for now. >> > >> > - Lack of key functions in some Instruction classes causing build >> > failures without -fno-rtti >> > (http://lists.llvm.org/pipermail/llvm-dev/2015-August/089010.html). No >&gt...

Hi Bill, there are a couple of things I didn't understand about your proposal, for example how it interacts with inlining, whether it is feasible to do the "turn invoke-of-Unwind_Resume into a branch" optimization and also whether in "resumedest" you still plan to use _Unwind_Resume to continue unwinding up the stack. Could you please show what the LLVM IR would look like

> On Jan 17, 2017, at 12:44 PM, Stephen Checkoway <s at pahtak.org> wrote: > > >> On Jan 17, 2017, at 14:39, Mehdi Amini <mehdi.amini at apple.com> wrote: >> >> >>> On Jan 17, 2017, at 12:33 PM, Stephen Checkoway <s at pahtak.org> wrote: >>> >>> >>>> On Jan 17, 2017, at 10:11, Mehdi Amini via llvm-dev

...throw 78; 7 } 8 catch (int){ 9 10 std::cout << "at catch\n"; 11 12 } 13 } LLVM-IR: $ llvm-g++ -S -emit-llvm eh1.catch.cpp -o eh1.catch.ll ... 46 define i32 @main() { 47 entry: 48 %0 = tail call i8* @__cxa_allocate_exception(i32 4) nounwind ; <i8*> [#uses=2] 49 %1 = bitcast i8* %0 to i32* ; <i32*> [#uses=1] 50 store i32 78, i32* %1, align 4 51 invoke void @__cxa_throw(i8* %0, i8* bitcast (%struct.__fundamental_type_info_pseudo* @_ZTIi to i8*), vo...

....file "test.ii" .text .globl main .align 2 .type main,%function main: push {r11, lr} mov r11, sp sub sp, sp, #24 mov r0, #0 str r0, [r11, #-4] mov r1, #4 str r0, [sp, #4] mov r0, r1 bl __cxa_allocate_exception mov r1, #20 str r1, [r0] ldr r1, .LCPI0_0 ldr r2, [sp, #4] bl __cxa_throw .align 2 .LCPI0_0: .long _ZTIi .Ltmp0: .size main, .Ltmp0-main .type .L.str,%object .section .rodata.str1.1,"aMS",%progbits,1 .L.str:...

...; preds = %entry %0 = bitcast i8* %D.2324_1 to i32 (...)*** store i32 (...)** getelementptr inbounds ([5 x i32 (...)*]* @_ZTVSt9exception, i64 0, i64 2), i32 (...)*** %0, align 8 %D.2306_4 = bitcast i8* %D.2324_1 to %struct.exception* %D.2305_5 = tail call i8* @__cxa_allocate_exception(i64 8) nounwind %D.2318_6 = bitcast i8* %D.2305_5 to %struct.exception** store %struct.exception* %D.2306_4, %struct.exception** %D.2318_6, align 8 invoke void @__cxa_throw(i8* %D.2305_5, i8* bitcast (%struct.__pointer_type_info_pseudo* @_ZTIPSt9exception to i8*), void (i8*)* null) noret...

-------------- next part -------------- An embedded message was scrubbed... From: "Mikael Lyngvig" <mikael at lyngvig.org> Subject: Re: [LLVMdev] An alternate implementation of exceptions Date: Sun, 6 Sep 2009 09:53:29 +0200 (CEST) Size: 6388 URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20090906/ca20be9e/attachment.eml>

Hello, Why does LLVM use __gcc_personality_v0 instead of __gxx_personality_v0 function when it lowers llvm.gcroot intrinsic? For my try-catch codegen I use last one (so does clang) and it conflicts with __gcc_personality_v0 produced by LLVM? I know how to solve it with my own GC plug-in, just wondering. And what's the difference between these two functions anyway? Thanks,

Hi Kenneth, this way of implementing unwind won't interact properly with dwarf exception handling. That's rather bad. Ciao, Duncan.