search for: 28h

...t the extra XMM stores; I thought the alignment was working, though... > Though the most problematic stuff is the lack of 'shadow zone' support > in Win64 ABI. Or maybe I haven't figured out how to turn this on. In > Win64 any function can treat 32 bytes of stack (RSP+08h..RSP+28h just > after the call instruction) as scratch data. VC++ compiler stores > arguments passed in registers there. In debug builds this doesn't get > optimized away. Wow, that's really strange... I'm pretty sure that simply isn't implemented. -Eli

...ug mode) randomly crashes on some simple hello-world-alike tests due to misalignment. Though the most problematic stuff is the lack of 'shadow zone' support in Win64 ABI. Or maybe I haven't figured out how to turn this on. In Win64 any function can treat 32 bytes of stack (RSP+08h..RSP+28h just after the call instruction) as scratch data. VC++ compiler stores arguments passed in registers there. In debug builds this doesn't get optimized away. Consider this C++ code: #include <stdio.h> int main () { for ( int i=0; i<5; i++ ) printf ( "%d\n", 0 ); return...

...galev<peter at shugalev.com> > wrote: >> Though the most problematic stuff is the lack of 'shadow zone' >> support >> in Win64 ABI. Or maybe I haven't figured out how to turn this on. In >> Win64 any function can treat 32 bytes of stack (RSP+08h..RSP+28h just >> after the call instruction) as scratch data. VC++ compiler stores >> arguments passed in registers there. In debug builds this doesn't get >> optimized away. > > Wow, that's really strange... I'm pretty sure that simply isn't > implemented. Anto...

...> > 15D10012 sub esp,4Ch > > 15D10015 mov eax,dword ptr [esp+60h] > > 15D10019 movups xmm0,xmmword ptr [eax] > > 15D1001C movaps xmmword ptr [esp+8],xmm0 ß why did this > become a movaps? > > 15D10021 movups xmmword ptr [esp+28h],xmm0 > > 15D10026 mov esi,dword ptr [esp+58h] > > 15D1002A mov edi,dword ptr [esp+5Ch] > > 15D1002E mov dword ptr [esp],40000000h > > 15D10035 call X86CompilationCallback (1335030h) > > > > Thanks for the help! > > > &...

...ores and loads have align 1 on them. ... 15D10012 sub esp,4Ch 15D10015 mov eax,dword ptr [esp+60h] 15D10019 movups xmm0,xmmword ptr [eax] 15D1001C movaps xmmword ptr [esp+8],xmm0 <-- why did this become a movaps? 15D10021 movups xmmword ptr [esp+28h],xmm0 15D10026 mov esi,dword ptr [esp+58h] 15D1002A mov edi,dword ptr [esp+5Ch] 15D1002E mov dword ptr [esp],40000000h 15D10035 call X86CompilationCallback (1335030h) Thanks for the help! Chuck. -------------- next part -------------- An HTML atta...

...ugalev.com> >> wrote: >>> Though the most problematic stuff is the lack of 'shadow zone' >>> support >>> in Win64 ABI. Or maybe I haven't figured out how to turn this on. In >>> Win64 any function can treat 32 bytes of stack (RSP+08h..RSP+28h just >>> after the call instruction) as scratch data. VC++ compiler stores >>> arguments passed in registers there. In debug builds this doesn't get >>> optimized away. >> Wow, that's really strange... I'm pretty sure that simply isn't >> imp...

Nueva publicación en blog: Cursos, "Curso a distancia: Estadística con ?R? para Profesionales de la Salud. ", por vaamonde en 21/10/13 13:28h Ver el blog en: http://r-es.org/tiki-view_blog_post.php?blogId=4&postId=76 Si no desea recibir estas notificaciones siga este enlace: http://r-es.org/tiki-user_watches.php?id=49 --- Comunidad R Hispano http://www.r-es.org

...*2. Setting atime from FUSE Mount:[davids at gluster-test1 gluster0]# touch test[davids at fgluster-test1 gluster0]# sudo touch -a -t 197001010001 test[davids at gluster-test1 gluster0]# stat test File: ?test? Size: 0 Blocks: 0 IO Block: 131072 regular empty fileDevice: 28h/40d Inode: 11420445633475641741 Links: 1Access: (0644/-rw-r--r--) Uid: ( 0/ root) Gid: ( 0/ root)Access: 2106-02-07 06:29:16.000000000 +0100Modify: 2018-01-05 09:15:28.655599273 +0100Change: 2018-01-05 09:15:48.744780537 +0100 Birth: -* *3. Setting atime from SMB Clie...

Hi folks! Running a dictionary program I get the following message before I get to the interesting part of the win program: err:int21:DOS3Call int21: unknown/not implemented parameters: int21: AX 5001, BX 01d7, CX 0437, DX 0000, SI 01e0, DI 03e7, DS 03af, ES 0437 wine: Unhandled exception, starting debugger err:seh:EXC_DefaultHandling Unhandled exception code c0000005 flags 0 addr 0x402a4c37

...ug mode) randomly crashes on some simple hello-world-alike tests due to misalignment. Though the most problematic stuff is the lack of 'shadow zone' support in Win64 ABI. Or maybe I haven't figured out how to turn this on. In Win64 any function can treat 32 bytes of stack (RSP+08h..RSP+28h just after the call instruction) as scratch data. VC++ compiler stores arguments passed in registers there. In debug builds this doesn't get optimized away. Consider this C++ code: #include <stdio.h> int main () { for ( int i=0; i<5; i++ ) printf ( "%d\n", 0 ); return...

...call writehex8 ;DEB < call crlf ;DEB < %endif < < mov bx, trackbuf ;DEB < call getonesec ;DEB get the Boot Catalog < < mov eax, dword [trackbuf+28h] ;DEB put RBA sector address in EAX < mov dword [bi_file], eax ;DEB Put RBA address into bi_file variable < < %ifdef DEBUG_MESSAGES < mov si,rba_loc_msg ;DEB write out RBA sector address < call writemsg...

...mov cs:byte_60106E, 0CDh .text:000000000040057E mov cs:byte_60106D, 0BFh .text:0000000000400585 mov cs:byte_60106C, 1Bh .text:000000000040058C mov cs:byte_60106B, 0E4h .text:0000000000400593 mov cs:byte_60106A, 28h .text:000000000040059A mov cs:byte_601069, 56h .text:00000000004005A1 mov cs:byte_601068, 0ACh .text:00000000004005A8 mov rax, 0F61EA263E1103088h .text:00000000004005B2 mov cs:Plaintext, rax .text:00000000004005B9...

...add esp, 8 00760D69 mov ds:dword_75D720, eax 00760D6E movzx ecx, ds:word_75D5F2 00760D75 cmp ecx, eax 00760D77 jbe loc_760EFC 00760D7D mov ecx, ds:dword_75D704 00760D83 imul eax, 28h 00760D86 mov eax, [eax+ecx+34h] 00760D8A sub eax, [ebp-4] 00760D8D cmp ds:dword_75D734, 2 00760D94 mov [ebp-14h], eax ; ; If (*(long *)75D734) != 2 then skip the call to ; VirtualProtect ; 00760D97 jnz...

All, When calling an invalid number using, I expect to hear: "dooh-deeh-daah We're sorry you have reached a number which has been disconnected ..." And that is indeed what I hear when I dial out from [*] using analog FXO, or VoicePulse or NuPhone. When I dial that same number trough the T1 / PRI interface however, I continually hear ringing, and then the call gets hungup. Any ideas

Hello. We''re currently using a Sun Blade1000 (2x750MHz, 1G ram, 2x160MB/s mpt scsi buses, skge GigE network) as a NFS backend with ZFS for distribution of free software like Debian (cdimage.debian.org, ftp.se.debian.org) and have run into some performance issues. We are running SX snv_48 and have run with a raidz2 with 7x300G for a while now, just added another 7x300G raidz2 today but