On 24 dec 2003, at 00:39, Peter Vreman wrote:
From today the default calling convention for i386 is changed from
stdcall
(the default since 1.9.0) to register calling. This means that you
have to
look at how assembler code loads the arguments and maybe store them
yourself in local variables.
I try to download last 1.9 sources but cannot access FPC archives via FTP, your
server (ftp://ftp.freepascal.org) seems to be down. What is happened with it?
--
Best regards,
Pavelmailto:[EMAIL PROTECTED]
___
fpc-devel
Bad news :(
Is this true for all {$mode }'s or only {$mode delphi} ?
On Wed, 24 Dec 2003, Peter Vreman wrote:
}Hi all,
}
}From today the default calling convention for i386 is changed from stdcall
}(the default since 1.9.0) to register calling. This means that you have to
}look at how assembler
Hello Ingmar,
Wednesday, December 24, 2003, 1:21:32 PM, you wrote:
IT Bad news :(
IT Is this true for all {$mode }'s or only {$mode delphi} ?
Why bad, Try to add {$calling oldfpccall} into your source
--
Best regards,
Pavelmailto:[EMAIL PROTECTED]
On Wed, 24 Dec 2003, Pavel V. Ozerski wrote:
}IT Bad news :(
}
}IT Is this true for all {$mode }'s or only {$mode delphi} ?
}
}Why bad, Try to add {$calling oldfpccall} into your source
Just personal taste, nothing else :) No, I'm not complaining, do what
you find is right.
Anyway, has someone
Hello!
On Wednesday 24 December 2003 13:00, Ingmar Tulva wrote:
Anyway, has someone actually analyzed how benefitial register calling
convention is? Sure it provides huge speed boost in case of a function
which adds two arguments together and returns the result - or is it so
sure? In fact, I
On Wednesday 24 December 2003 16:36, Anton Tichawa wrote:
This example still does not include the benefits within procedure
my_function, namely the saving of instruction extension words with stack
offsets. In that case, 2 memory accesses (to the instruction extension word
and to the stack
