search for: longjmp

On 28 April 2015 at 00:30, Reid Kleckner <rnk at google.com> wrote: > I think Paweł identified the problem. The frames on the stack between the > setjmp and longjmp must have valid unwind information, which is described > here: > https://msdn.microsoft.com/en-us/library/ft9x1kdx.aspx?f=255&MSPPError=-2147217396 > > In particular, it has this line about JITed code: > "For dynamically generated functions [JIT compilers], the runtime to...

Hi, I have some code which has sigsetjmp / longjmp. After a longjmp, unreachable is inserted, which is fine. The problem is that in the backend before calling longjmp, some register was spilled to a stack location which is live across the jmp. I mean, it will be live after jumping. The stack location was initialized before the call to setjmp, and i...

Thanks to the hard work of Bill Wendling (wendling at isanbard.org), LLVM now translates setjmp/longjmp calls into the LLVM "exception handling" instructions invoke & unwind. This means that all of the LLVM optimizers are now aware of the extra control flow edges made possible by setjmp & longjmp, so data flow analyses won't make incorrect transformations. A variety of testcas...

...be compiled >> to native code using llvm. It calls, and is called by, the other >> subsystems, many of which have to be compiled using gcc because they >> use small amounts of inline assembly. All of the subsystems catch >> and throw errors to one another using setjmp/longjmp. >> >> When gcc-built code calls longjmp(), the destination might be a >> setjmp() in llvm-built code, and vice versa. At present the >> gcc-built code uses the setjmp/longjmp implementations provided >> by the gnu C library; and presumably the llvm-built code wi...

...stly legacy C code). One subsystem will be compiled to native code using llvm. It calls, and is called by, the other subsystems, many of which have to be compiled using gcc because they use small amounts of inline assembly. All of the subsystems catch and throw errors to one another using setjmp/longjmp. When gcc-built code calls longjmp(), the destination might be a setjmp() in llvm-built code, and vice versa. At present the gcc-built code uses the setjmp/longjmp implementations provided by the gnu C library; and presumably the llvm-built code will use llvm's setjmp/longjmp intrinsics. Are...

[klibc] [PATCH] fix ARM longjmp with zero 'val'. We need to set the condition codes on the ARM. The previous version was using a left over condition code from the caller. Also, use conditional execution to eliminate branch and reduce size. Signed-off-by: Bill Pringlemeir <bpringle at sympatico.ca> diff --git a/...

...g/?p=libs/klibc/klibc.git;a=commit;h=d7d16afbdae9bdea83aeb26ac572e6fc4d7d4940 Author: Steve McIntyre <steve at einval.com> AuthorDate: Fri, 29 Jun 2012 18:13:34 +0100 Committer: maximilian attems <max at stro.at> CommitDate: Sun, 1 Jul 2012 22:51:00 +0200 [klibc] arm/setjmp.S: fix longjmp There's a real bug in the ARM assembly version of longjmp in usr/klibc/arch/arm/setjmp.S: it will always pass back its first argument as a return value, even if it's 0 (see the man page for more details). Oddly, the Thumb implementation in the same file *is* correct! Signed-off-by: Steve...

On Oct 4, 2011, at 3:53 PM, Eli Friedman wrote: > On Tue, Oct 4, 2011 at 3:10 PM, Khaled ElWazeer > <khalid.alwazeer at gmail.com> wrote: >> Hi, >> >> I have some code which has sigsetjmp / longjmp. After a longjmp, unreachable >> is inserted, which is fine. The problem is that in the backend before >> calling longjmp, some register was spilled to a stack location which is live >> across the jmp. I mean, it will be live after jumping. The stack location >> was initiali...

I'm trying to make sense in the support for setjmp/longjmp in Clang and LLVM, with only partial success. I'll try to summarize my findings in the hope that someone can shed some light on why things are the way they are and what I'm missing. Clang. Clang recognizes two forms of setjmp (all I say here applies to longjmp similarly): * __builtin_setj...

Do the LLVM Setjmp/Longjmp intrinsics interact with C++ exception handling and execute C++ cleanup actions? I compiled a small example using setjmp/longjmp using clang and they did not execute C++ cleanup actions and calling longjmp bypassed calling destructors on objects that were allocated between the call to setjmp and l...

On Tue, Oct 4, 2011 at 3:10 PM, Khaled ElWazeer <khalid.alwazeer at gmail.com> wrote: > Hi, > > I have some code which has sigsetjmp / longjmp. After a longjmp, unreachable > is inserted, which is fine. The problem is that in the backend before > calling longjmp, some register was spilled to a stack location which is live > across the jmp. I mean, it will be live after jumping. The stack location > was initialized before the c...

...std %r2,0(%r3) /* save TOC pointer (not needed) */ @@ -43,17 +47,28 @@ setjmp: std %r31,8(%r3) li %r3,0 /* indicate success */ blr /* return */ +#if _CALL_ELF == 2 + .size setjmp,.-setjmp +#else + .size setjmp,.-.setjmp +#endif - .size .setjmp,.-.setjmp + .text + .balign 4 + .globl longjmp +#if _CALL_ELF == 2 + .type longjmp, at function +longjmp: +#else .section ".opd","aw" + .balign 8 longjmp: - .quad .longjmp,.TOC. at tocbase,0 + .quad .longjmp, .TOC. at tocbase, 0 .previous - .size longjmp,24 .type .longjmp, at function - .globl longjmp .globl .longjm...

...lesen <stoklund at 2pi.dk>wrote: > > On Oct 4, 2011, at 3:53 PM, Eli Friedman wrote: > > > On Tue, Oct 4, 2011 at 3:10 PM, Khaled ElWazeer > > <khalid.alwazeer at gmail.com> wrote: > >> Hi, > >> > >> I have some code which has sigsetjmp / longjmp. After a longjmp, > unreachable > >> is inserted, which is fine. The problem is that in the backend before > >> calling longjmp, some register was spilled to a stack location which is > live > >> across the jmp. I mean, it will be live after jumping. The stack >...

...std %r2,0(%r3) /* save TOC pointer (not needed) */ @@ -43,17 +47,28 @@ setjmp: std %r31,8(%r3) li %r3,0 /* indicate success */ blr /* return */ +#if _CALL_ELF == 2 + .size setjmp,.-setjmp +#else + .size setjmp,.-.setjmp +#endif - .size .setjmp,.-.setjmp + .text + .balign 4 + .globl longjmp +#if _CALL_ELF == 2 + .type longjmp, at function +longjmp: +#else .section ".opd","aw" + .balign 8 longjmp: - .quad .longjmp,.TOC. at tocbase,0 + .quad .longjmp, .TOC. at tocbase, 0 .previous - .size longjmp,24 .type .longjmp, at function - .globl longjmp .globl .longjm...

...S +++ klibc-1.5.20/usr/klibc/arch/arm/setjmp.S @@ -29,7 +29,11 @@ setjmp: stmia r0, {r4, r5, r6, r7, r8, r9, r10, fp, sp, lr} mov r0, #0 +#if defined (___ARM_ARCH_4T__) || defined (__ARM_ARCH_4__) mov pc, lr +#else + bx lr +#endif .size setjmp,.-setjmp .text @@ -39,7 +43,11 @@ setjmp: longjmp: ldmia r0, {r4, r5, r6, r7, r8, r9, r10, fp, sp, lr} mov r0, r1 +#if defined (___ARM_ARCH_4T__) || defined (__ARM_ARCH_4__) mov pc, lr +#else + bx lr +#endif .size longjmp,.-longjmp #else /* __thumb__ */ @@ -75,7 +83,11 @@ setjmp: mov r7, sp stmia r0!, {r3, r4, r5, r6, r7} mov r0,...

I'm trying to get unwind to work. I was unable to get an unwind example to work directly, so I decided to compile a c program that uses setjmp and longjmp and work backwards. I keep running into a "Abort trap" problem, whatever "Abort trap" is. Anyway, here's an example of a C program that compiles and works properly under normal gcc, but that fails with an "Abort trap" under LLVM: #include <setjmp.h> long...

It seems straightforward to implement, if it just needs to be functionally correct. I have another question about setjmp/longjmp. When the following program is compiled and run with argument 10 (./a.out 10), should it print 10 or 23? I am asking this question because it prints 23 when compiled with gcc and prints 10 when compiled with clang. If it is supposed to return 23, it seems to me that saving and clobbering registers...

Hi, In our (non-C) compiler we use setjmp/longjmp to implement exception handling. For the initial implementation LLVM backend, I'm keeping that model. In order to ensure that changes performed in a try/setjmp==0 block survive the longjmp, the changes must be done via volatile operations. Given that volatility is a property of individual load...

On Sun, Dec 18, 2016 at 02:23:01PM +0100, Jonas Maebe via llvm-dev wrote: > Recap: we use setjmp/longjmp for our exception handling on all platforms in > our regular (non-LLVM) code generators. I'd like to use the same > infrastructure with the LLVM code generator for code interoperability > purposes (the LLVM SjLj personality is not binary-compatible with our > existing setjump/longju...

...e: > >> >> On Oct 4, 2011, at 3:53 PM, Eli Friedman wrote: >> >> > On Tue, Oct 4, 2011 at 3:10 PM, Khaled ElWazeer >> > <khalid.alwazeer at gmail.com> wrote: >> >> Hi, >> >> >> >> I have some code which has sigsetjmp / longjmp. After a longjmp, >> unreachable >> >> is inserted, which is fine. The problem is that in the backend before >> >> calling longjmp, some register was spilled to a stack location which is >> live >> >> across the jmp. I mean, it will be live after jump...