[fpc-devel] Plans for 2022

2022-01-08 Thread J. Gareth Moreton via fpc-devel
Some people requested a Patreon post as to my plans for 2022 with FPC, so I was happy to oblige.  Plans may change a bit though depending on what happens in life and also what Florian's own vision is with the compiler, but this is the gist of it: https://www.patreon.com/posts/60922821 Gareth

Re: [fpc-devel] Double-checking an optimisation

2022-01-08 Thread J. Gareth Moreton via fpc-devel
On 09/01/2022 01:47, Martin Frb via fpc-devel wrote: I take it, it also is one (or two?) bytes longer? If that is in a loop, which otherwise is exactly within a 32 byte aligned block, then that could cause a slow down too. (If the loop is 16 bytes long, but aligned to a 32byte-bound+16, then

Re: [fpc-devel] Double-checking an optimisation

2022-01-08 Thread Martin Frb via fpc-devel
On 09/01/2022 01:37, J. Gareth Moreton via fpc-devel wrote: Hi everyone, So a merge request of mine was just approved that allows the peephole optimizer access to more registers when it needs one for temporary storage.  It allows it to make an optimisation on x86_64-win64 that wasn't possible

[fpc-devel] Double-checking an optimisation

2022-01-08 Thread J. Gareth Moreton via fpc-devel
Hi everyone, So a merge request of mine was just approved that allows the peephole optimizer access to more registers when it needs one for temporary storage.  It allows it to make an optimisation on x86_64-win64 that wasn't possible before due to the lack of available volatile registers.  In

[fpc-devel] Val() with unsigned variable

2022-01-08 Thread Bart via fpc-devel
Hi, There's been a hot debate in the bugtracker about fixing Val() for signed variables. There's a patch (in fact there are several), and an attempt to speed Val() up significantly by having helper functions for each type of input. It looks like this is going to be fixed soon (and hopefully be merg