search for: callssetjmp

...that callsFunctionThatReturnsTwice(): // If there are calls to setjmp or sigsetjmp, don't perform stack slot // coloring. The stack could be modified before the longjmp is executed, // resulting in the wrong value being used afterwards. (See // <rdar://problem/8007500>.) if (MF.callsSetJmp()) return false; It might be possible for register coalescing to break something as well. /jakob

...turnsTwice(): > > // If there are calls to setjmp or sigsetjmp, don't perform stack slot > // coloring. The stack could be modified before the longjmp is executed, > // resulting in the wrong value being used afterwards. (See > // <rdar://problem/8007500>.) > if (MF.callsSetJmp()) > return false; > > It might be possible for register coalescing to break something as well. > > /jakob > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20111004/797531bc/attachmen...

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

...gt;> // If there are calls to setjmp or sigsetjmp, don't perform stack slot >> // coloring. The stack could be modified before the longjmp is executed, >> // resulting in the wrong value being used afterwards. (See >> // <rdar://problem/8007500>.) >> if (MF.callsSetJmp()) >> return false; >> >> It might be possible for register coalescing to break something as well. >> >> /jakob >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attach...

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 is used afterwards. Is there any bug in handling

Good evening, Kenneth. Thank you to apply (and rewrite my naive code better) and to file the issue to http://llvm.org/bugs/show_bug.cgi?id=7304 I have checked r105528 at this morning. I think the pass must be still cleaned up and rewritten. There are my two proposals for enhancement. 1) To separate Specialization(and rewriting callsites) to other module. It would be better if new module were