Re: [fpc-devel] Policy on platform-specific compiler code

2020-10-17 Thread J. Gareth Moreton via fpc-devel
Apologies, Jonas; I hope I didn't come off as condescending or rude in that last e-mail - I was joking because while my algorithm is faster, a few nanoseconds probably isn't going to cut it in the grand scheme of things! I got my code to work, treating "magic add" in the same way as the exist

Re: [fpc-devel] Policy on platform-specific compiler code

2020-10-17 Thread J. Gareth Moreton via fpc-devel
Well, I think you might be right on this one, Jonas! I've tested my algorithm against the one used in the compiler. It's 5 times faster when used with small divisors (so loop iterations are minimal)... but that amounts to about 15 nanoseconds compared to 75 nanoseconds!  Additionally, it treat

Re: [fpc-devel] Policy on platform-specific compiler code

2020-10-16 Thread J. Gareth Moreton via fpc-devel
On 16/10/2020 10:47, Jonas Maebe via fpc-devel wrote: On 16/10/2020 10:14, J. Gareth Moreton via fpc-devel wrote: Before I go optimising the wrong thing, I have a question to ask. What's the policy on platform-specific assembly language in the compiler, or any code designed to run on a specific

Re: [fpc-devel] Policy on platform-specific compiler code

2020-10-16 Thread Jonas Maebe via fpc-devel
On 16/10/2020 10:14, J. Gareth Moreton via fpc-devel wrote: > Before I go optimising the wrong thing, I have a question to ask.  > What's the policy on platform-specific assembly language in the > compiler, or any code designed to run on a specific (source) platform > (and using a more generic imp

[fpc-devel] Policy on platform-specific compiler code

2020-10-16 Thread J. Gareth Moreton via fpc-devel
Hi everyone, Before I go optimising the wrong thing, I have a question to ask.  What's the policy on platform-specific assembly language in the compiler, or any code designed to run on a specific (source) platform (and using a more generic implementation otherwise via $ifdef)?  I ask because