@srvaldez You are going deeper than I am prepared to go. I will stay with your previous instructions unless you advise otherwise. I should imagine most will do the same. Your opening post did not bode well for gcc/clang, but with 11.2.0 gcc/clang we have a different story. It is a serious competitor...

Found one.

Release Notes

fbc 1.20.0 [2 April 2024] LLVM 18.1.3 [5 April 2024]

FreeBASIC-1.20.0-gcc-11.2.0cl (162MiB)

I have tried to find a 'changelog' for LLVM 18.1.3, but I cannot find one.

Blimey — feedback! I need a lie down.

Thank you, antarman.

srvaldez should get the credit. He supplied the engine — I just did the coachwork.

Sleep 1, Sleep 2, …, Sleep 15 all give a Sleep of 15 because Sleep is linked to the System Clock (64Hz). To get Sleep n to sleep for n milliseconds, then use: Declare Function settimer Lib "winmm" Alias "timeBeginPeriod"(As Ulong=1) As Long settimer That uses a timer with a frequ...

Use Randomize , 5

Why? Why not

Tee surface — Redirect input to multiple surfaces.

What would we do without srvaldez?

Unless I am mistaken, it looks like the compile time for the new gcc 11.2.0/clang is about half of what it was. It still takes longer than gcc, but for a lot of code published on the forum the difference may not be that noticeable. It is still worthwhile to develop in gas because that gives blisteri...

Regarding srvaldez's instructions. The llvm downloads are now 20240320 from 20240308 updated three days ago. The libLLVM.dll is now libLLVM-18.dll. My HASH program is now 2% faster than the previous clang using gcc 11.2.0/clang so we are pulling away further from gcc 9.3. My PRNG plot program lookin...

@dodicat

Really nice indeed.

Off-topic, but I had a look at fbc 1.20.0/gcc 11.2.0/clang vs fbc 1.10.1/gcc 9.3

Here are the binaries in KiB. clang likes 64-bit.

I take it that you were able to compile Encrypternet with clang? Three posts back: “My Encrypternet application isn't benefitting from a clang build, but that is wall-to-wall Microsoft cryptographic APIs.” At over 140MiB per second, the only thing which can improve on that is a more powerful CPU. :)

This where I have ended up: It also keeps life simple by just having two toolchains.

Performance wise, it is anyone's guess who wins: gcc 9.3 or gcc 11.2/clang.

On further tests, a gcc 11.2/clang is not much faster than gcc 9.3/clang using 64-bit. It is worth it for 32-bit with gcc 11.2/clang being about 4% faster than gcc 11.2. 32-bit gcc 9.3/clang is deplorable compared with gcc 9.3. I have no idea why. That is with my plot program. On balance, there is a...