ispc VS Beef

This so-called GPU programming model has existed many decades before the appearance of the first GPUs, but at that time the compilers were not so good like the CUDA compilers, so the burden for a programmer was greater.

As another poster has already mentioned, there exists a compiler for CPUs which has been inspired by CUDA and which has been available for many years: ISPC (Implicit SPMD Program Compiler), at https://github.com/ispc/ispc .

NVIDIA has the very annoying habit of using a lot of terms that are different from those that have been previously used in computer science for decades. The worst is that NVIDIA has not invented new words, but they have frequently reused words that have been widely used with other meanings.

SIMT (Single-Instruction Multiple Thread) is not the worst term coined by NVIDIA, but there was no need for yet another acronym. For instance they could have used SPMD (Single Program, Multiple Data Stream), which dates from 1988, two decades before CUDA.

Moreover, SIMT is the same thing that was called "array of processes" by C.A.R. Hoare in August 1978 (in "Communicating Sequential Processes"), or "replicated parallel" by Occam in 1985 or "PARALLEL DO" by "OpenMP Fortran" in 1997-10 or "parallel for" by "OpenMP C and C++" in 1998-10.

The only (but extremely important) innovation brought by CUDA is that the compiler is smart enough so that the programmer does not need to know the structure of the processor, i.e. how many cores it has and how many SIMD lanes has each core. The CUDA compiler distributes automatically the work over the available SIMD lanes and available cores and in most cases the programmer does not care whether two executions of the function that must be executed for each data item are done on two different cores or on two different SIMD lanes of the same core.

ISPC: https://github.com/ispc/ispc

Have you looked at [ISPC - Intel SPMD Program Compiler][0]?

  [0]: https://github.com/ispc/ispc

Is it really a one man show? It looks like Beef Lang has excellent home page https://www.beeflang.org/ and I never heard about it until now.

Jai is dead, this is the year of Beef from the genius behind Plants vs. Zombies and Bookworm Adventures Deluxe.

On one hand, I feel there are so many similar languages out there {(Val, Vala, Vale, Corroded Iron, Beef, Zig, Carbon, cppfront, Jai)...}, that we don't need yet another, but also I encourage further thought because it may be inspiration for future improvements to C++ itself. The number one faux pas I see them make is trying to directly compete with C++ (inventing their own type system, their standard library, their build system, own package format...), whereas your (by its very nature as a transpiler) embraces C++.

This project is an exploration of two things. Firstly I wanted to dig into the exciting new language and IDE, Beef. If you're the low-level code oriented type I _highly_ recommend checking it out. Beef is a systems-level language (like C/C++) that borrows heavily from C# but ditches the garbage collector. It comes with a wonderful IDE and a great debugger and just an excellent work flow. Check it out at https://www.beeflang.org/.

[Beef](https://www.beeflang.org/): memory management with first-class allocators.

Had a very slow computer at the time and needed to convert lots of pixels and emulate a little processor (SPC700). So I wrote the utilities in x86 assembly. Eventually I got tired of that and decided to move up the chain some 😅... Today I still write using C++ because nothing else has really come along that satisfies my desire for low level control and perf, short of possibly Beef or Rust (but it's too obnoxiously opinionated for me, and the community seems allergic to useability/interoperability improvements, with the arrogant tone coming across as "well why don't you just rewrite it from scratch in pure Rust" 🤦‍♀️ - that said, I'd love to adopt a few features from it into C++).

Beef https://www.beeflang.org/