Displaying 20 results from an estimated 113 matches for "qword".
Did you mean:
word
2016 May 23
2
[BUG] Mismatch between assembler & disassembler of X86 RIP-relative instruction
Hi,
I found a mismatch between assembler & disassembler of X86: I assembled an
instruction, then disassembled the output, but the result is not the same
as the first original code: "add qword ptr [205163983024656], 1" vs " add
qword ptr [1985229328], 1"
Anybody knows what is wrong?
Thanks.
$ echo "ADD QWORD PTR [0xba9876543210], 0x1"|llvm-mc -assemble
-triple=x86_64 -x86-asm-syntax=intel -output-asm-variant=1
--show-encoding
add qword ptr [20516398302...
2016 May 23
0
[BUG] Mismatch between assembler & disassembler of X86 RIP-relative instruction
...n Mon, May 23, 2016 at 2:44 PM, Jun Koi <junkoi2004 at gmail.com> wrote:
> Hi,
>
> I found a mismatch between assembler & disassembler of X86: I assembled an
> instruction, then disassembled the output, but the result is not the same
> as the first original code: "add qword ptr [205163983024656], 1" vs " add
> qword ptr [1985229328], 1"
>
> Anybody knows what is wrong?
>
> Thanks.
>
>
> $ echo "ADD QWORD PTR [0xba9876543210], 0x1"|llvm-mc -assemble
> -triple=x86_64 -x86-asm-syntax=intel -output-asm-variant=1
> --s...
2014 Mar 25
3
[LLVMdev] Getting the Debugging JIT-ed Code with GDB example to work
I'm trying to run the example described at:
http://llvm.org/docs/DebuggingJITedCode.html
I followed the sample command line session (below, with versions numbers
for everything), but gdb doesn't stop at the breakpoints as described. Any
idea what is wrong?
Thanks,
Zach
zdevito at derp:~/terra/tests$
> ~/clang+llvm-3.4-x86_64-unknown-ubuntu12.04/bin/clang -cc1 -O0 -g
>
2016 Oct 17
2
Dict proxy client returning empty string instead of multiline string
...t;> RDI: 0x683288 --> 0x7ffff7653120 --> [...] (pool)
> > > >>>>>> RAX: 0x0 (result)
> > > >>>>>>
> > > >>>>>> 0x7ffff73a384f: nop
> > > >>>>>> 0x7ffff73a3850: mov rsi,QWORD PTR [rsp+0x8]
> > > >>>>>> 0x7ffff73a3855: mov rdi,r14
> > > >>>>>> => 0x7ffff73a3858: call 0x7ffff736d3c0 <p_strdup at plt>
> > > >>>>>> 0x7ffff73a385d: mov QWORD PTR [r13+0x0],rax
> > >...
2016 Oct 16
2
Dict proxy client returning empty string instead of multiline string
...<dict_lookup+48>: jmp rax
Before the call to p_strdup in "client_dict_lookup":
RSI: 0x6832d8 ("test\r\ntest") (lookup.result.value)
RDI: 0x683288 --> 0x7ffff7653120 --> [...] (pool)
RAX: 0x0 (result)
0x7ffff73a384f: nop
0x7ffff73a3850: mov rsi,QWORD PTR [rsp+0x8]
0x7ffff73a3855: mov rdi,r14
=> 0x7ffff73a3858: call 0x7ffff736d3c0 <p_strdup at plt>
0x7ffff73a385d: mov QWORD PTR [r13+0x0],rax
0x7ffff73a3861: mov rsi,QWORD PTR [rsp+0x18]
0x7ffff73a3866: xor rsi,QWORD PTR fs:0x28
0x7ffff73a386f: mov eax,ebx...
2020 Aug 30
5
BUG: complete misunterstanding of the MS-ABI
...re: why is the return
value mapped to an XMM register, but not the arguments?
Microsoft's CL.EXE -c -Ox generates the following (of course)
CONFORMANT code:
__udivmodti4 proc public
; Line 10
test r9, r9
je SHORT $LN1 at udivmodti4
; Line 11
mov rax, QWORD PTR [r8]
mov QWORD PTR [r9], rax
mov rax, QWORD PTR [r8+8]
mov QWORD PTR [r9+8], rax
$LN1 at udivmodti4:
; Line 12
mov rax, QWORD PTR [rdx]
mov QWORD PTR [rcx], rax
mov rax, QWORD PTR [rdx+8]
mov QWORD PTR [rcx+8],...
2016 Oct 17
2
Dict proxy client returning empty string instead of multiline string
...up in "client_dict_lookup":
>>
>> RSI: 0x6832d8 ("test\r\ntest") (lookup.result.value)
>> RDI: 0x683288 --> 0x7ffff7653120 --> [...] (pool)
>> RAX: 0x0 (result)
>>
>> 0x7ffff73a384f: nop
>> 0x7ffff73a3850: mov rsi,QWORD PTR [rsp+0x8]
>> 0x7ffff73a3855: mov rdi,r14
>> => 0x7ffff73a3858: call 0x7ffff736d3c0 <p_strdup at plt>
>> 0x7ffff73a385d: mov QWORD PTR [r13+0x0],rax
>> 0x7ffff73a3861: mov rsi,QWORD PTR [rsp+0x18]
>> 0x7ffff73a3866: xor rsi,QWORD P...
2012 Feb 14
0
[LLVMdev] Strange behaviour with x86-64 windows, bad call instruction address
...that the 3 that work all have JIT function pointer addresses less than a 32 bit value but the one that is failing has a 64 bit address, as indicated in the snippet below:
000007FFFFC511D7 pop rbp
000007FFFFC511D8 ret
000007FFFFC511D9 sub rsp,20h
000007FFFFC511DD mov rcx,qword ptr [rbp-70h]
000007FFFFC511E1 mov edx,0FFFFFFFEh
000007FFFFC511E6 xor r8d,r8d
000007FFFFC511E9 call rsi
000007FFFFC511EB add rsp,20h
000007FFFFC511EF test al,1
000007FFFFC511F2 je 000007FFFFC511C3
000007FFFFC511F8 sub rsp,20h
000007FFFF...
2016 Oct 17
2
Dict proxy client returning empty string instead of multiline string
...up.result.value)
> >>>>>> RDI: 0x683288 --> 0x7ffff7653120 --> [...] (pool)
> >>>>>> RAX: 0x0 (result)
> >>>>>>
> >>>>>> 0x7ffff73a384f: nop
> >>>>>> 0x7ffff73a3850: mov rsi,QWORD PTR [rsp+0x8]
> >>>>>> 0x7ffff73a3855: mov rdi,r14
> >>>>>> => 0x7ffff73a3858: call 0x7ffff736d3c0 <p_strdup at plt>
> >>>>>> 0x7ffff73a385d: mov QWORD PTR [r13+0x0],rax
> >>>>>> 0x7ffff73a...
2019 Oct 25
4
unnecessary reload of 8-byte struct on i386
...nction Assembler::emit_arith receives a struct (Operand) by value and passes it by value to another function. That struct is 8 bytes long, so the -O3 generated code uses movsd to copy it up the stack. However, we end up with some loads that aren't needed, as in the following chunk:
movsd xmm0, qword ptr [ecx] # xmm0 = mem[0],zero
mov dword ptr [esp + 24], edx
movsd qword ptr [esp + 40], xmm0
movsd xmm0, qword ptr [esp + 40] # xmm0 = mem[0],zero
movsd qword ptr [esp + 8], xmm0
As far as I can tell, the fourth line has no effect. On its own, that seems like a small missed opportunity for optimi...
2016 Oct 17
1
Dict proxy client returning empty string instead of multiline string
...up":
>>>
>>> RSI: 0x6832d8 ("test\r\ntest") (lookup.result.value)
>>> RDI: 0x683288 --> 0x7ffff7653120 --> [...] (pool)
>>> RAX: 0x0 (result)
>>>
>>> 0x7ffff73a384f: nop
>>> 0x7ffff73a3850: mov rsi,QWORD PTR [rsp+0x8]
>>> 0x7ffff73a3855: mov rdi,r14
>>> => 0x7ffff73a3858: call 0x7ffff736d3c0 <p_strdup at plt>
>>> 0x7ffff73a385d: mov QWORD PTR [r13+0x0],rax
>>> 0x7ffff73a3861: mov rsi,QWORD PTR [rsp+0x18]
>>> 0x7ffff73a3866...
2018 Jan 14
1
PCIe ordering and new VIRTIO packed ring format.
Hi,
I have a concern about the portability of offloading the new VIRTIO packed ring format to hardware.
According to the PCIe rev 2.0, paragraph 2.4.2. Update Ordering and Granularity Observed by a Read Transaction"
" if a host CPU writes a QWORD to host memory, a Requester reading that QWORD from host memory may observe a portion of the QWORD updated and another portion of it containing the old value."
This means that after the device reads a 16byte descriptor, it cannot know that all the values In the descriptor are up to date even...
2016 Oct 17
2
Dict proxy client returning empty string instead of multiline string
...x6832d8 ("test\r\ntest") (lookup.result.value)
> >>>> RDI: 0x683288 --> 0x7ffff7653120 --> [...] (pool)
> >>>> RAX: 0x0 (result)
> >>>>
> >>>> 0x7ffff73a384f: nop
> >>>> 0x7ffff73a3850: mov rsi,QWORD PTR [rsp+0x8]
> >>>> 0x7ffff73a3855: mov rdi,r14
> >>>> => 0x7ffff73a3858: call 0x7ffff736d3c0 <p_strdup at plt>
> >>>> 0x7ffff73a385d: mov QWORD PTR [r13+0x0],rax
> >>>> 0x7ffff73a3861: mov rsi,QWORD PTR [rsp+...
2011 Mar 19
2
[LLVMdev] Apparent optimizer bug on X86_64
...users should not rely upon it. Assigning to YYVAL
1313 unconditionally makes the parser a bit smaller, and it avoids a
1314 GCC warning that YYVAL may be used uninitialized. */
1315 yyval = yyvsp[1-yylen];
=> 0x0000000000400c2d <rpcalc_parse+653>: movsd xmm0,QWORD PTR
[rbx+rax*8]
0x0000000000400c32 <rpcalc_parse+658>: movsd QWORD PTR
[rbp-0x808],xmm0
As far as I understand it, assigning to eax zero-extends to rax.
However, eax holds the result of "1-yylen" which is expected to be
negative, so it should be sign-extended before usin...
2016 May 02
3
[PATCH] MSVC2015U2 workaround, version 2
...fixes a problem with MSVC2105 update2,
but it doesn't disable any optimization, so the resulting encoding
performance should be almost unaffected by this workaround.
MSVC compiles
abs_residual_partition_sums[partition] = (FLAC__uint32)_mm_cvtsi128_si32(mm_sum);
into this:
movq QWORD PTR [rsi], xmm2
while it should be
movd eax, xmm2
mov QWORD PTR [rsi], rax
With this patch, MSVC emits
movq QWORD PTR [rsi], xmm2
mov DWORD PTR [rsi+4], r9d
so the price of this workaround is 1 extra write instruction per partition.
-------------- next part --...
2005 Mar 11
0
[LLVMdev] FP Intrinsics
...ord ptr ds:[161D6248h],0
17160431 mov dword ptr ds:[161D624Ch],0
1716043B mov eax,76E4560h
17160440 mov dword ptr [esp],eax
17160443 call HueVMReadCommands_LLVMReadVoxel (19BB229h)
17160448 fsub dword ptr ds:[161D6280h]
1716044E fabs
17160450 fst qword ptr [esp+14h]
17160454 ftst
17160456 fstp st(0)
17160458 fnstsw ax
1716045A sahf
1716045B fldz
1716045D fchs
1716045F fld qword ptr [esp+14h]
17160463 fucomip st,st(1)
17160465 fstp st(0)
17160467 jbe 17160498
1716046D mov eax,76E4F60h
17160...
2019 Jun 25
3
Potential missed optimisation with SEH funclets
...it seems like the unwind funclets generated by LLVM are much larger than those generated by Microsoft’s CL compiler.
I used the following code as a test:
void test() {
MyClass x;
externalFunction();
}
Compiling with CL, the unwind funclet that destroys ‘x’ is just two lines of asm:
lea rcx, QWORD PTR x$[rdx]
jmp ??1MyClass@@QEAA at XZ
However when compiling with clang-cl, it seems like it sets up an entire function frame just for the destructor call:
mov qword ptr [rsp + 16], rdx
push rbp
.seh_pushreg 5
sub rsp, 32
.seh_stackalloc 32
Lea rbp, [rdx + 48]
.seh_endprologue
Lea rcx, [rbp - 16...
2012 Mar 02
3
[LLVMdev] Access Violation using ExecutionEngine on 64-bit Windows 8 Consumer Preview
...problem after updating to Windows 8 Consumer
Preview recently. It seems that LLVM inserts 4 calls to the same
function at the start of generated code. The function's disassembly
(taken from nearby computer with Windows 7) is:
00000000773A0DD0 sub rsp,10h
00000000773A0DD4 mov qword ptr [rsp],r10
00000000773A0DD8 mov qword ptr [rsp+8],r11
00000000773A0DDD xor r11,r11
00000000773A0DE0 lea r10,[rsp+18h]
00000000773A0DE5 sub r10,rax
00000000773A0DE8 cmovb r10,r11
00000000773A0DEC mov r11,qword ptr gs:[10h]
00000000773A0DF5 cmp...
2011 Mar 19
0
[LLVMdev] Apparent optimizer bug on X86_64
...ely upon it. Assigning to YYVAL
> 1313 unconditionally makes the parser a bit smaller, and it avoids a
> 1314 GCC warning that YYVAL may be used uninitialized. */
> 1315 yyval = yyvsp[1-yylen];
> => 0x0000000000400c2d <rpcalc_parse+653>: movsd xmm0,QWORD PTR
> [rbx+rax*8]
> 0x0000000000400c32 <rpcalc_parse+658>: movsd QWORD PTR
> [rbp-0x808],xmm0
>
>
> As far as I understand it, assigning to eax zero-extends to rax.
> However, eax holds the result of "1-yylen" which is expected to be
> negative, so i...
2006 Apr 15
1
Begin with Autocompleter
...== 4) {
29 if (http_request.status == 200) {
30 alert(http_request.responseText);
31 } else {
32 alert(''Han ocurrido problemas con la petición.'');
33 }
34 }
35 }
In search_ajax.php file I find the element in the database:
<?php
$query = isset ( $_POST[''qword''] ) ? trim ( rtrim ( $_POST[''qword''] ) ) : null;
if ( $query != null ){
$db->Execute(" SELECT * FROM table WHERE field LIKE ''%". $query ."%'' ") or die($db->ErrorMsg());
$elements = array();
while ( $record = $db->fetch...