Displaying 2 results from an estimated 2 matches for "15d10021".
Did you mean:
15d10012
2007 Oct 19
0
[LLVMdev] movaps being generated despite alignment 1 being specified
...mp() / print().
Evan
>
>
> …
>
> 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)
>
>
>
> Tha...
2007 Oct 18
3
[LLVMdev] movaps being generated despite alignment 1 being specified
...s suddenly
become a movaps? All the stores 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.
-------------- nex...