search for: jns

...%reg1230<kill> 324 %reg1055<dead> = LEA64r %reg1047, 1, %reg1053, 0 328 %reg1135 = MOVSX64rr32 %reg1025 332 %reg1136 = MOV64rr %reg1135<kill> 336 %reg1136 = ADD64ri32 %reg1136, -4, %EFLAGS<imp-def,dead> 340 TEST64rr %reg1136<kill>, %reg1136, %EFLAGS<imp-def> 344 JNS mbb<file solve.f, line 23, in loop at depth 1, bb16,0x83a2c70>, %EFLAGS<imp-use,kill> Here we have the curious case of %reg1055 being defined and then immediately killed. It's a dead assignment. Why it wasn't removed I don't know, but the LiveInterval looks like this:...

As read here : http://www.sns.ias.edu/~jns/security/iptables/iptables_conntrack.html modprobe ip_conntrack_ftp would give me the ability to use active ftp if I have (pseudo/simplified code) iptables -A FORWARD -i eth0 -m state --state ESTABLISHED,RELATED -j ACCEPT iptables -A FORWARD -j DROP but I cant use active ftp, WHAT IS WRONG.. et...

...%reg1055<dead> = LEA64r %reg1047, 1, %reg1053, 0 > 328 %reg1135 = MOVSX64rr32 %reg1025 > 332 %reg1136 = MOV64rr %reg1135<kill> > 336 %reg1136 = ADD64ri32 %reg1136, -4, %EFLAGS<imp-def,dead> > 340 TEST64rr %reg1136<kill>, %reg1136, %EFLAGS<imp-def> > 344 JNS mbb<file solve.f, line 23, in loop at depth 1, > bb16,0x83a2c70>, > %EFLAGS<imp-use,kill> David, could you post the live ins/outs for the block? My thinking is that %reg1055 may be live through the block. -- Christopher Lamb -------------- next part -------------- An HTML...

...mov %edx,(%eax) 280: f6 c1 40 ​ ​ test $0x40,%cl 283: 74 08 je 28d <t_run_test+0x28d> 285: 81 ca 08 04 00 00 or $0x408,%edx 28b: 89 10 mov %edx,(%eax) 28d: 84 c9 test %cl,%cl 28f: 0f 89 34 01 00 00 jns 3c9 <t_run_test+0x3c9> After ​ r252152:​ Note that the OR $0x408 and OR $0x810 come ​now ​ in reverse order. 35d: 81 c9 08 04 00 00 or $0x408,%ecx 363: 89 4c 24 28 mov %ecx,0x28(%esp) 367: 89 df mov %ebx,%edi 369: 83 e7 10 ​ ​ and...

...dsw %%mm2, %%mm0 \n\t" /* add+128 and saturate to 16bit */ +" packuswb %%mm1, %%mm0 \n\t" /* pack saturate with next(high) four values */ +" movq %%mm0, (%0) \n\t" /* writeback */ +" lea (%0,%2), %0 \n\t" /*_dst+_dst_ystride */ +" jns 1b \n\t" /* loop */ + : "+r" (_dst) + : "r" (_residue), + "r" (_dst_ystride) + : "memory", "ecx" ); +} + + +void oc_frag_recon_inter__mmx(unsigned char *_dst,int _dst_ystride, + const unsigned char *_src,int _src_ystride,const ogg_int1...

...dsw %%mm2, %%mm0 \n\t" /* add+128 and saturate to 16bit */ +" packuswb %%mm1, %%mm0 \n\t" /* pack saturate with next(high) four values */ +" movq %%mm0, (%0) \n\t" /* writeback */ +" lea (%0,%2), %0 \n\t" /*_dst+_dst_ystride */ +" jns 1b \n\t" /* loop */ + : "+r" (_dst) + : "r" (_residue), + "r" (_dst_ystride) + : "memory", "ecx" ); +} + + +void oc_frag_recon_inter__mmx(unsigned char *_dst,int _dst_ystride, + const unsigned char *_src,int _src_ystride,const ogg_int1...

...%reg1055<dead> = LEA64r %reg1047, 1, %reg1053, 0 > 328 %reg1135 = MOVSX64rr32 %reg1025 > 332 %reg1136 = MOV64rr %reg1135<kill> > 336 %reg1136 = ADD64ri32 %reg1136, -4, %EFLAGS<imp-def,dead> > 340 TEST64rr %reg1136<kill>, %reg1136, %EFLAGS<imp-def> > 344 JNS mbb<file solve.f, line 23, in loop at depth 1, > bb16,0x83a2c70>, > %EFLAGS<imp-use,kill> > > Here we have the curious case of %reg1055 being defined and then > immediately > killed. It's a dead assignment. Why it wasn't removed I don't > know, b...

...fa_register %rbp subq $16, %rsp movq $0, -16(%rbp) movq $1, -8(%rbp) .align 16, 0x90 .LBB8_1: # %label_1 # =>This Inner Loop Header: Depth=1 movq -8(%rbp), %rcx movq %rsp, %rax addq $-16, %rax movq %rax, %rsp testq %rcx, %rcx jns .LBB8_3 # BB#2: # %abs_then # in Loop: Header=BB8_1 Depth=1 negq %rcx .LBB8_3: # %abs_else # in Loop: Header=BB8_1 Depth=1 movq %rcx, (%rax) movq (%rax)...

Hello all I hope you can help with the following problem I am tryint to keep win98 and Win2K profiles seperate in a users home directory and at the same time be able to use net use /HOME. I cannot do it. Is it possible? the more i test profiles the more confused i get. one situation is this logon home = \\%L\%U\ logon path = \\%L\%U\ntprofile The above config will store the nt profile

Maybe adjust this to be different for –Os, -Oz than for –O2? Kevin Smith From: llvm-dev [mailto:llvm-dev-bounces at lists.llvm.org] On Behalf Of James Molloy via llvm-dev Sent: Friday, November 20, 2015 4:05 PM To: Steve King <steve at metrokings.com>; Renato Golin <renato.golin at linaro.org> Cc: llvm-dev <llvm-dev at lists.llvm.org> Subject: Re: [llvm-dev] Recent -Os code

...al_head+9/e0> <===== 0: 8b 56 04 mov 0x4(%esi),%edx <===== Code; c0165e6c <__journal_remove_journal_head+c/e0> 3: 85 d2 test %edx,%edx Code; c0165e6e <__journal_remove_journal_head+e/e0> 5: 79 23 jns 2a <_EIP+0x2a> c0165e93 <__journal_remove_journal_head+33/e0> Code; c0165e70 <__journal_remove_journal_head+10/e0> 7: 68 c7 fd 22 c0 push $0xc022fdc7 Code; c0165e75 <__journal_remove_journal_head+15/e0> c: 68 bc 06 00 00 push $0x6bc...

...(%dx),%es:(%edi) > 601: 69 61 73 5f 73 65 74 imul $0x7465735f,0x73(%ecx),%esp > 608: 5f pop %edi > 609: 65 6e outsb %gs:(%esi),(%dx) > - 60b: 74 72 je 67f <__FUNCTION__.20731+0xe> > - 60d: 79 00 jns 60f <__FUNCTION__.22630> > + 60b: 74 72 je 67f <__FUNCTION__.20645+0xe> > + 60d: 79 00 jns 60f <__FUNCTION__.22543> > > -0000060f <__FUNCTION__.22630>: > - 60f: 77 72 ja 683 <__FUNCTION__.20731+0...

...ti" #define CLI_STI_CLOBBERS -#define CLI_STI_INPUT_ARGS #endif /* CONFIG_PARAVIRT */ /* @@ -59,27 +58,26 @@ static inline void __raw_spin_lock_flags { asm volatile( "\n1:\t" - LOCK_PREFIX " ; decb %[slock]\n\t" + LOCK_PREFIX " ; decb %0\n\t" "jns 5f\n" "2:\t" - "testl $0x200, %[flags]\n\t" + "testl $0x200, %1\n\t" "jz 4f\n\t" STI_STRING "\n" "3:\t" "rep;nop\n\t" - "cmpb $0, %[slock]\n\t" + "cmpb $0, %0\n\t" "jle 3b\n\t&q...

...ti" #define CLI_STI_CLOBBERS -#define CLI_STI_INPUT_ARGS #endif /* CONFIG_PARAVIRT */ /* @@ -59,27 +58,26 @@ static inline void __raw_spin_lock_flags { asm volatile( "\n1:\t" - LOCK_PREFIX " ; decb %[slock]\n\t" + LOCK_PREFIX " ; decb %0\n\t" "jns 5f\n" "2:\t" - "testl $0x200, %[flags]\n\t" + "testl $0x200, %1\n\t" "jz 4f\n\t" STI_STRING "\n" "3:\t" "rep;nop\n\t" - "cmpb $0, %[slock]\n\t" + "cmpb $0, %0\n\t" "jle 3b\n\t&q...

The saga continues. I've been tracking the interface changes and merging them with the refactoring work I'm doing. I got as far as building stage3 of llvm-gcc but the object files from stage2 and stage3 differ: warning: ./cc1-checksum.o differs warning: ./cc1plus-checksum.o differs (Are the above two ok?) The list below is clearly bad. I think it's every object file in the

Hi folks, Here is the result of the latest work on the pvops front, after the x86 arch merge. From the functionality point of view, almost nothing was changed, except for proper vsmp support - which was discussed, but not implemented before - and the introduction of smp_ops in x86_64, which eased the merging of the smp header. Speaking of the merge, a significant part (although not majority) of

Hi folks, Here is the result of the latest work on the pvops front, after the x86 arch merge. From the functionality point of view, almost nothing was changed, except for proper vsmp support - which was discussed, but not implemented before - and the introduction of smp_ops in x86_64, which eased the merging of the smp header. Speaking of the merge, a significant part (although not majority) of

...g??M>T0)dh9j3 at KSB zI5lIm#2ty-4^Z4*ND93Va^m(dV6&P>=Zncu$~kIGb=k+4 at _=|JYUCg(XQ^@cwv&|C z4~}w{a=+)iZW{rVawr%=C>T)6RU at F3vlv^&^Y<WuYeWL)kiC~OhcD%mXSL(=AkB|o zwS|Jr4(2P!s5Og6x93oLpxpeBCsPg9OXr<5nqPGUa7*Q(G%xy8yEViCnE4;n?oq#- z>s-4p<)hZ{hWfqg0KaNZSEzU_zV#>GNxII;jNs+mF?`KC8)<jvX-Lj#zPOEdjpJoT zCyjGKgISE^<!fKy-WdwS!Lv{xW;*r?K5aluEkR7p at mCe|GY?Ev8ITxWMqL&_d2sOc z`C>A`uex=*H&11|W!w#4h-fq%(&*UOQMc#w<X>=4J|mpN$Zy94erA)<sU{HkUgt#g zws_ulo)D^vr%mLf`@q!jC at 1-yKHN!uJ^57~0NM#CX8FkejP2&x71{~NwhfSNP;HWS zK|3KtcH&oPCk`J~=ADJ)tw)AUM...