search for: elwazeer

..." }; I think if I add mine to this list, it should work. I will try that. Thanks, -Khaled On Tue, Oct 4, 2011 at 7:15 PM, Jakob Stoklund Olesen <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, so...

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...

Actually my problem is solved when I added "__sigsetjmp" to this list. Thanks, -Khaled On Tue, Oct 4, 2011 at 10:27 PM, Khaled ElWazeer <khalid.alwazeer at gmail.com>wrote: > > That code should do it, but I realized you only detect setjmp functions by > name. My code is calling "__sigsetjmp" not "segsetjmp". You only support > these functions: > > static const char *ReturnsTwiceFns[] =...

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

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 &g...

On Oct 4, 2011, at 8:23 PM, Khaled ElWazeer wrote: > Actually my problem is solved when I added "__sigsetjmp" to this list. Rafael just added a returns_twice function attribute to LLVM IR. I expect he will update the callsFunctionThatReturnsTwice() function soon. /jakob

Hi, I need some documentation on how to use the LLVM X86 intrinsics for SSE support -like "x86_sse2_movnt_dq/x86_ssse3_pshuf_b/..." How to use them as functions in the code, and what are the correct argument types / return value types for each? Could anybody point me to where I can find this documentation? Thanks, -Khaled -------------- next part -------------- An HTML attachment was