I usually start performance investigations by compiling with '-al', and
looking at the generated assembler.
Regards,
Peter
P.S. From what we know so far, inclined to agree with Charlie.
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http:/
I defined a static array to convert the mode 13h VGA palette to separate red,
green and blue to send to aggpas as well as the packed RGB565 format needed to
send to ptcgraph 16bit colors.
James
Type
VGARGBRec= Record
R,G,B:Byte;
RGB:Word;
end;
Const
VGA25
El 04/07/2017 a las 11:09, Anthony Walter escribió:
I can convert to static buffers and get good performance (if I know the
text isn't changing), but I'm now curious if this specific performance
issue is related to fpc's for loop code generation.
What do you think?
Hello,
AFAIK the problem
Hi,
On Tue, 4 Jul 2017, Anthony Walter wrote:
> I think the code to generate the geometry each frame isn't that complex,
> and I pre-allocate room in my buffer for all the geometry just once, so
> it seems doing to calculations for the geometry is what's killing the
> performance. The calculation
I recall earlier this year some people in this mailing list were discussing
surprising performance problems with fpc and for loops. I wanted to know if
this is still an existing problem as I am experiencing some unusual
performance degradation related to a for loop in one of my test
applications.