search for: 40h

...movaps xmm1,xmmword ptr [xx] 00413500 mulps xmm1,xmm0 00413503 movaps xmm0,xmmword ptr [ebp-60h] 00413507 addps xmm0,xmm1 0041350A movaps xmmword ptr [ebp-60h],xmm0 269: 270: mem[1] = _mm_move_ss(mem[1], mem[2]); 0041350E movaps xmm0,xmmword ptr [ebp-40h] 00413512 movaps xmm1,xmmword ptr [ebp-50h] 00413516 movss xmm1,xmm0 0041351A movaps xmmword ptr [ebp-50h],xmm1 271: mem[1] = _mm_shuffle_ps(mem[1], mem[1], 0x39); 0041351E movaps xmm0,xmmword ptr [ebp-50h] 00413522 movaps xmm1,xmmword ptr [ebp-50h] 004135...

..._bug.cgi?id=3739. I checked out the revision the patch was created for (66183) and applied it but the assembler generated seems to fail whenever it reaches a movaps insctruction. eg. movaps xmmword ptr [rsp+20h],xmm8 movaps xmmword ptr [rsp+30h],xmm7 movaps xmmword ptr [rsp+40h],xmm6 Would this have something to do with the stack alignment? I am wondering if anybody else has had any success using that patch to get Windows x64 JIT to work correctly. Or if my problem may be unrelated. Any suggestions would be useful.

...argc, char** argv) { if (argc != 2) return -1; int r = solve((int) strtol(argv[1], NULL, 10)); printf("%d solutions\n", r); } ``` clang 3.5's result: ``` public _main _main proc near var_48 = qword ptr -48h var_40 = qword ptr -40h var_34 = dword ptr -34h push rbp push r15 push r14 push r13 push r12 push rbx sub rsp, 18h mov ebx, 0FFFFFFFFh cmp...

...t;> printf("%d solutions\n", r); >> } >> ``` >> >> clang 3.5's result: >> >> ``` >> public _main >> _main proc near >> >> var_48 = qword ptr -48h >> var_40 = qword ptr -40h >> var_34 = dword ptr -34h >> >> push rbp >> push r15 >> push r14 >> push r13 >> push r12 >> push rbx >> s...

Nueva publicación en blog: Cursos, "Estadística Básica Para la Investigación Biomédica", por Xavi en 16/01/14 09:40h Ver el blog en: http://r-es.org/tiki-view_blog_post.php?blogId=4&postId=79 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

...` >>>> >>>> clang 3.5's result: >>>> >>>> ``` >>>> public _main >>>> _main proc near >>>> >>>> var_48 = qword ptr -48h >>>> var_40 = qword ptr -40h >>>> var_34 = dword ptr -34h >>>> >>>> push rbp >>>> push r15 >>>> push r14 >>>> push r13 >>>> push r12 >&gt...

...81D300B0 sub rsp,rax 0000000581D300B3 mov byte ptr [rcx+94h],0 0000000581D300BA mov eax,10h 0000000581D300BF call 00000005F08425D0 0000000581D300C4 sub rsp,rax 0000000581D300C7 mov byte ptr [rcx+94h],0 0000000581D300CE add dword ptr [rcx+40h],2 0000000581D300D2 mov rsp,rbp 0000000581D300D5 pop rbp 0000000581D300D6 ret The function located at 0x00000005F08425D0 is not valid (according to visual studio: 00000005F08425D0 ?? ??). If I compile LLVM bytecode using llc, this function is __chkstk: .def fn_0000...

Since lot of people want this thing, I will try to take a stab at it. For now, I will hard code the menu in the code, and then somebody else can remove that restriction. May be we can add some kind of keyword to the config file which syslinux ignores and the comboot menu does something with it. I have one question about comboot: If I write a DOS program using C (compiled using watcom -3 -mt -osx

...> 0000000581D300B3 mov byte ptr [rcx+94h],0 > 0000000581D300BA mov eax,10h > 0000000581D300BF call 00000005F08425D0 > 0000000581D300C4 sub rsp,rax > 0000000581D300C7 mov byte ptr [rcx+94h],0 > 0000000581D300CE add dword ptr [rcx+40h],2 > 0000000581D300D2 mov rsp,rbp > 0000000581D300D5 pop rbp > 0000000581D300D6 ret > > The function located at 0x00000005F08425D0 is not valid (according to > visual studio: 00000005F08425D0 ?? ??). > > If I compile LLVM bytecode using llc, this function...

...e see details above. * What makes you suited to carry the project? Several years of experience in Linux kernel development as reflected by previous and on-going projects. * How much time do you plan to invest in the project before, during and after the Summer of Code (We expect full time 40h/week during GSoC, but better make this explicit)? I will be working full-time on this project and plan to continue working till it gets merged into mainline (and then continue as maintainer) * Please provide a schedule of how this time will be spent on subtasks of the project. While this is o...

...e see details above. * What makes you suited to carry the project? Several years of experience in Linux kernel development as reflected by previous and on-going projects. * How much time do you plan to invest in the project before, during and after the Summer of Code (We expect full time 40h/week during GSoC, but better make this explicit)? I will be working full-time on this project and plan to continue working till it gets merged into mainline (and then continue as maintainer) * Please provide a schedule of how this time will be spent on subtasks of the project. While this is o...

...Manufacturer : American Power Conversion - Product : Smart-UPS C 1000 FW:UPS 10.0 / ID=1005 - Serial Number: 3S1520X04472 bLength: 18 bDescriptorType: 01h bcdUSB: 0200h bDeviceClass: 00h bDeviceSubClass: 00h bDeviceProtocol: 00h bMaxPacketSize0: 40h idVendor: 051Dh idProduct: 0003h bcdDevice: 0106h iManufacturer: 1 iProduct: 2 iSerialNumber: 3 bNumConfigurations: 1 wTotalLength: 41 bNumInterfaces: 1 bConfigurationValue: 1 iConfiguration: 0 bmAttributes:...

...xmm2,xmm7 002E01CA addpd xmm2,xmm6 002E01CE movapd xmm5,xmmword ptr [esp+80h] 002E01D7 subpd xmm5,xmm1 002E01DB subpd xmm5,xmm3 002E01DF mulpd xmm0,xmmword ptr ds:[2E0010h] 002E01E7 subpd xmm5,xmm0 002E01EB movapd xmm6,xmmword ptr [esi+2C0040h] 002E01F3 mulpd xmm6,xmm5 002E01F7 addpd xmm6,xmm2 002E01FB addpd xmm6,xmmword ptr [esi+2C0050h] 002E0203 fld qword ptr [esp+0E0h] 002E020A call 76719BA1 CALL 002E020F imul edi,eax,0Ch 002E0212 lea ecx,[edi+3] First...

...+ shr cx,5 ; Number of entries left +.scanentry: + cmp byte [gs:si],0 + jz .fail + cmp word [gs:si+11],0Fh ; Long filename + jne .short_entry + +.vfat_entry: + push eax + push ecx + push si + push di +.vfat_ln_info: ; Get info about the line that we're on + mov al,[gs:si] + test al,40h + jz .vfat_tail_ln + and al,03Fh + mov ah,1 ; On beginning line + jmp .vfat_ck_ln + +.vfat_tail_ln: ; VFAT tail line processing (later in VFAT, head in name) + test al,80h ; Invalid data? + jnz .vfat_abort + mov ah,0 ; Not on beginning line + cmp dl,al + jne .vfat_abort ; Is this the entry...

...+ shr cx,5 ; Number of entries left +.scanentry: + cmp byte [gs:si],0 + jz .fail + cmp word [gs:si+11],0Fh ; Long filename + jne .short_entry + +.vfat_entry: + push eax + push ecx + push si + push di +.vfat_ln_info: ; Get info about the line that we're on + mov al,[gs:si] + test al,40h + jz .vfat_tail_ln + and al,03Fh + mov ah,1 ; On beginning line + jmp .vfat_cp_ln + +.vfat_tail_ln: ; VFAT tail line processing (later in VFAT, head in name) + test al,80h ; Invalid data? + jnz .vfat_abort + mov ah,0 ; Not on beginning line + cmp dl,al + jne .vfat_abort ; Is this the entry...

Good day to all, Gert Hulselmans requested a feature for MDISKCHK.COM that would function roughly like GETARGS.COM[1] by Murali Krishnan Ganapathy: DOS SET command output for MEMDISK kernel arguments passed by previous boot-loaders. He also needed to support the case for MEMDISK-in-a-MEMDISK type situations, where all MEMDISK kernel arguments could be gathered together and output as a list

Hmm, I'm not able to get those .ll files to compile if I disable SSE and I end up with SSE instructions(including sqrtpd) if I don't disable it. On Thu, Jul 18, 2013 at 10:53 PM, Peter Newman <peter at uformia.com> wrote: > Is there something specifically required to enable SSE? If it's not > detected as available (based from the target triple?) then I don't think