Displaying 6 results from an estimated 6 matches for "alwazeer".
Did you mean:
elwazeer
2011 Oct 04
2
[LLVMdev] setjmp - longjmp
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
&...
2011 Oct 05
0
[LLVMdev] setjmp - longjmp
...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, some register was spilled to a s...
2011 Oct 04
0
[LLVMdev] setjmp - longjmp
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...
2011 Oct 05
1
[LLVMdev] setjmp - longjmp
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[] = {
> "_s...
2011 Oct 04
3
[LLVMdev] setjmp - longjmp
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
2006 Mar 15
1
does include not outomaticaly exclude not matching files ?
Hello,
I was trying to syncronize two directories with --include="*800*" or "800*"
or "/800*", but I always et the same file list. Does option --include not
outomaticaly exclude not matching files ?
/usr/local/bin/rsync -n --include="800*" --rsh=remsh
--rsync-path=/usr/local/bin/rsync -rzpogctS --log-format=%f /data/DWG/N/5225
plot1:/data/DWG/N
building