> For example, if I have changes in separate files that I want to split up, how
> might one go about it without manually modiying the patch files? (As an easy
> example, I split up the uComplex patches into two... one with the alignment
> and vectorcall changes, and the other with the "const"
Well, when it comes to the specific changes I made to uComplex... the
compiler might be able to detect a kind of 'auto-const' system, but
actually inserting 'const' into the formal parameters helps with syntax
checking as well as generating more efficient code, namely modifying the
parameter
Am 29.10.19 um 14:06 schrieb Marco van de Voort:
Op 2019-10-27 om 10:46 schreef Florian Klämpfl:
Am 27.10.19 um 10:27 schrieb Michael Van Canneyt:
If you genuinely believe that micro-optimization changes can make a
difference:
Submit patches.
As said: I am against applying them. Why?
A partial example of where "condition_in" shows its power (compiled code
from fpc\packages\fcl-base\src\advancedipc.pp)
BEFORE:
...
jb .Lj178
subl $17,%eax
cmpl $26,%eax
jb .Lj178
cmpl $30,%eax
stc
je .Lj178
subl $32,%eax
cmpl
Hi everyone,
So after my x86_64 optimizer overhaul was rejected in its current form,
I decided to set to work again in cleaner steps. The first thing I've
started to address are jump optimisations, since they gave notable
improvements that were independent of things lke the reduction in the
