Vincent Snijders wrote:
Hi,
I am looking at some shootout benchmarks and I have the following
question. Look at the following program:
program loop;
{$mode objfpc}
var
d: array[0..$FFF] of double;
di: PDouble;
i: integer;
c: double;
begin
c := 125;
i := low(d);
Florian Klaempfl schreef:
Line 17 generates two assembler instructions. Line 22 generates three
assembler instructions. As far as I can see both high(d) and @d[high(d)]
are constants, because d is a global variable.
Is it possible that line 22 will generate 2 assembler instructions in
the
Lee, John wrote:
Does this mean we can't do snapshot on win32? Is there a fix planned? Eg
couldn't we write a fpc version of cp - guess this would only be a few
lines or is it more complicated than this?
1) Do you get this error too when building Win32 snapshots?
2) It certainly doesn't mean
Does this mean we can't do snapshot on win32? Is there a fix planned? Eg
couldn't we write a fpc version of cp - guess this would only be a few
lines or is it more complicated than this?
This situation is there already for years.
___
fpc-pascal
Vincent Snijders wrote:
Florian Klaempfl schreef:
Line 17 generates two assembler instructions. Line 22 generates three
assembler instructions. As far as I can see both high(d) and @d[high(d)]
are constants, because d is a global variable.
Is it possible that line 22 will generate 2
