So far, I'm researching the optimisation as listed below... tracking
registers with identical values and changing them to minimise pipeline
stalls. Because I don't need to keep track of their actual values, just
whether they've changed since a particular MOV instruction, I've managed to
move this
On 03.06.2018 17:11, Florian Klämpfl wrote:
Am 21.05.2018 um 20:58 schrieb Ondrej Pokorny:
In this (your) case I don't expect anything - it is one of FPC's
favorites "undefined behaviour" because as documented, it is not
allowed to change the loop variable value within a for loop.
Yes, just
Am 21.05.2018 um 20:58 schrieb Ondrej Pokorny:
In this (your) case I don't expect anything - it is one of FPC's favorites "undefined behaviour" because as documented,
it is not allowed to change the loop variable value within a for loop.
Yes, just asking :)
In my case (without the I:=1 ass
Am 21.05.2018 um 21:05 schrieb J. Gareth Moreton:
Would you object to me trying anyway, Florian?
No, feel free to go ahead, but it needs to be done step by step.
It might be that I run into the same problems you had and it's too
unsafe, but I'm going by a conservative philosophy in that if it
