Re: I need speed! Byte-for-byte comparing ...
- From: "jukka@xxxxxxxxxxxx" <jukka@xxxxxxxxxxxx>
- Date: 23 Mar 2006 02:57:48 -0800
Yeah... Don't we want jz?
That's true, I noticed that and corrected already.. a big mistake. :(
..more:
mov edx, [esi]
mov eax, [esi+4]
xor edx, [edi]
xor eax, [edi+4]
add esi, 8
add edi, 8
or edx, eax
jz .more
That gives few percent more boost, but the effect is very neglible..
one instruction less, possibly little bit less dependencies between
registers. I don't know, but this should be pretty close to how fast we
can read from the memory.. the "or" is only extra that springs to mind
in loop which is structured like this. I could be wrong, just a hunch
and besides there are so many flavours of x86 already anyway. :)
Eg. the difference computation should be practically free with this
kind of arrangement. The next step is MMX.. anyone care to guess if
and/or how much that will speed things up?
.
- References:
- I need speed! Byte-for-byte comparing ...
- From: Dave Turner
- Re: I need speed! Byte-for-byte comparing ...
- From: jukka@xxxxxxxxxxxx
- Re: I need speed! Byte-for-byte comparing ...
- From: randyhyde@xxxxxxxxxxxxx
- Re: I need speed! Byte-for-byte comparing ...
- From: jukka@xxxxxxxxxxxx
- Re: I need speed! Byte-for-byte comparing ...
- From: randyhyde@xxxxxxxxxxxxx
- Re: I need speed! Byte-for-byte comparing ...
- From: jukka@xxxxxxxxxxxx
- Re: I need speed! Byte-for-byte comparing ...
- From: Frank Kotler
- I need speed! Byte-for-byte comparing ...
- Prev by Date: Re: RosAsm Bliss, and NASM Bliss
- Next by Date: Re: bits 32 oddities in NASM
- Previous by thread: Re: I need speed! Byte-for-byte comparing ...
- Next by thread: lea and addressing
- Index(es):
Relevant Pages
|