On Thursday 02 of June 2011 22:36:53 Florian Klämpfl wrote:
> Am 01.06.2011 22:07, schrieb Michalis Kamburelis:
> > Hi,
> >
> > In my tests, FPC 2.4.4 has much slower CompareMem than FPC 2.4.2, at
>
> > least for some cases:
> I've commited an improved version in r17642
Is this merged in 2.4.5 ?
Florian Klämpfl wrote:
>
> I improved CompareDWord as well, for your application it should be even
> better.
>
Ha, I hesitated earlier to mention that CompareWord and CompareDWord are
~4 times slower than equivalent (on the same number of bytes)
CompareMem/CompareByte calls :) Cool, times with l
Am 03.06.2011 03:06, schrieb Michalis Kamburelis:
> Florian Klämpfl wrote:
>> Am 01.06.2011 22:07, schrieb Michalis Kamburelis:
>>> Hi,
>>>
>>> In my tests, FPC 2.4.4 has much slower CompareMem than FPC 2.4.2, at
>>> least for some cases:
>>
>> I've commited an improved version in r17642
>
> That'
Florian Klämpfl wrote:
> Am 01.06.2011 22:07, schrieb Michalis Kamburelis:
>> Hi,
>>
>> In my tests, FPC 2.4.4 has much slower CompareMem than FPC 2.4.2, at
>> least for some cases:
>
> I've commited an improved version in r17642
That's great :) I just tested with fpc from SVN (rev 17644), and ca
Am 01.06.2011 22:07, schrieb Michalis Kamburelis:
> Hi,
>
> In my tests, FPC 2.4.4 has much slower CompareMem than FPC 2.4.2, at
> least for some cases:
I've commited an improved version in r17642
___
fpc-devel maillist - fpc-devel@lists.freepascal.or
Hello FPC,
Thursday, June 2, 2011, 7:03:10 PM, you wrote:
>> PlainCompare CompareByteXCompareByte
>> ---
>> Equal arrays 1000 elements 16250 ms 625 ms 656 ms
>> Diff. arrays 1000 el
Hello FPC,
Thursday, June 2, 2011, 7:03:10 PM, you wrote:
FK> Am 02.06.2011 18:45, schrieb José Mejuto:
>> Hello FPC,
>>
>> PlainCompare CompareByteXCompareByte
>> ---
>> Equal arrays 1000 elemen
Hello FPC,
Wednesday, June 1, 2011, 10:07:18 PM, you wrote:
MK> In my tests, FPC 2.4.4 has much slower CompareMem than FPC 2.4.2, at
MK> least for some cases:
Please take care with my last email, it has a bug that result in wrong
speed tests, anyway after fixing the bug, the "magic" number for p
Am 02.06.2011 18:45, schrieb José Mejuto:
> Hello FPC,
>
> PlainCompare CompareByteXCompareByte
> ---
> Equal arrays 1000 elements 16250 ms 625 ms 656 ms
> Diff. arrays 1000 elements
Hello FPC,
Wednesday, June 1, 2011, 10:07:18 PM, you wrote:
MK> In my tests, FPC 2.4.4 has much slower CompareMem than FPC 2.4.2, at
MK> least for some cases:
The difference is that CompareMem takes the same time to check a
memory block if the elements are equal or different, while the pascal
co
02.06.2011 19:49, Sven Barth пишет:
Maybe it's better if you or someone else would try to improve the performance
of the i386 assembler
code that makes up the Compare(Byte/Word/DWord) functions (it's located in
rtl/i386/i386.inc btw).
I tend to agree. The string instructions used there (rep c
On 01.06.2011 22:07, Michalis Kamburelis wrote:
Any thoughts? Maybe something can be improved?
1. Why CompareMem got slower in FPC 2.4.4? Maybe something can be fixed?
Let's see...
CompareMem in 2.4.2:
=== source begin ===
function CompareMem(P1, P2: Pointer; Length: cardinal): Boolean;
va
Hi,
In my tests, FPC 2.4.4 has much slower CompareMem than FPC 2.4.2, at
least for some cases:
# with fpc 2.4.4
$ time ./compare_mem_test 1
real0m7.795s
user0m7.764s
sys 0m0.008s
# with fpc 2.4.2
$ time ./compare_mem_test 1
real0m1.218s
user0m1.216s
sys 0m0
13 matches
Mail list logo
