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...

Some surprises here. With my 500MiB hash program there was no appreciable difference performance wise between 32-bit and 64-bit using either gcc 9.3 clang or gcc 11.2 clang. clang was about 7% faster in all cases compared with gcc. However it is worth noting that we are using a Microsoft API. With m...

Using srvaldez's instructions, I did a gcc 8.1.0/clang. I always liked gcc 8.3.0. Applying to various code, there was very little difference 8.1.0 vs 9.3.0 performance wise 32-bit or 64-bit. The 9.3.0 binaries were significantly smaller, which surprised me. 9.3.0/clang seems to be the better, but it...

After following srvaldez's build instructions, change the name of the toolchain to:

FreeBASIC-1.20.0-gcc-9.3.0cl

That will appear in WinFBE's Compiler Setup and

fbc 1.20.0 / gcc 9.3.0cl

will appear in SCS III's status bar.

Regarding SCS III. If you do not have the latest SCSII then you will need to drop DlgMsgBox.dll into your WinFBE Tools folder.

DlgMsgBox.zip

The dll is responsible for pixel perfect message box centring on the parent window and makes the message box multiple monitor aware.

When this project started, it was a rare event to get clang to compile anything. With fbc 1.20.0/9.3.0 and no asm in sight, it is compiling everything I throw at it. 9.3.0 gives much smaller binaries than 13.2.0 and 13.2.0 doesn't do anything for performance, in my experience. Don't get too excited ...

That seems easy enough. I wrote: "SCS III will swiftly follow" Compiled with fbc 1.10.1/gcc 9.3.0 with 32-bit -O2. The clang version was to show clang working. I use SetCompilerSwitchesIIILA.exe for a larger form font size and 10 point message boxes, as shown in the screenshot above. Sans ...

Arachnophilia wrote:When can you offer SCS III for download?

Without my anonymous toolchain author's permission, the answer to that is never, unless someone else goes public with their clang toolchain. With that, SCS III will swiftly follow. One thing is for sure, and that is I cannot do it.

Hashing a 500MiB file using SHA512/2 to give a 256-bit hash. gcc 2322ms clang 2328ms Nothing in it performance wise. So why am I halving a 512-bit hash? SHA512 was designed for 64-bit machines and is faster than SHA256 which was designed for 32-bit machines. SHA512/2 is about 13% faster than SHA256....

Using fbc 1.20.0/gcc 9.3.0 with -O2 optimization. 32-bit binaries in KIB gcc clang Dodicat pool 1085 1014 UEZ fireworks 602 566 How about compile times? Pool took 4.5 seconds with gcc and 13.3 seconds with clang. gas, on the other hand, took 0.5 seconds with a binary of 647 KiB. We all know that gas...

It may be a while before this hits the streets, as fbc 1.20.0 is still a work in progress. https://deltarho.org.uk/Downloads/scsiii.jpg The above was compiled using clang and the binary was 10% smaller than SCS II. I have some clang PRNGs outperforming gcc PRNGs in 64-bit mode. gcc still has the edg...

Thanks, srvaldez.

Your att seeding code is working a treat. “If it ain't broke, then don't fix it.”

With att I find the proliferation of %, ", and \n decided off-putting. At my time of life I try to avoid anything which proliferates

srvaldez wrote:,,,if one wanted to go that route...

I have written quite a bit of Z80, Motorola 68000 and Intel. It was not a difficult transition. I cannot see myself getting into att. Whoever designed att at AT&T needs locking up, unless they were locked up when they designed it.

Hi srvaldez. I cannot actually use HammingSeed64a. Firstly, I need a Uint64 return value. Secondly, if a time stamp fails a Hamming test, we go back and read the time stamp again. HammingSeed64a only passes the asm block once. I could try to adapt it, but I'd be in dangerous territory, not understan...