llvm-project VS zig

Whenever I try to build llvm with the following instructions wget https://github.com/llvm/llvm-project/releases/download/llvmorg-14.0.4/llvm-project-14.0.4.src.tar.xz mkdir build && cd build cmake ../llvm-project-14.0.4.src/llvm -DLLVM_ENABLE_PROJECTS="clang" -DCMAKE_INSTALL_PREFIX=/ make -j16 DESTDIR=../opt make install

Sounds awfully familiar to a bug I hit in lld where the xmm1 register was saved on the stack before calling into __delayLoadHelper2 but it was overriden during the call to __delayHelper2 and the restored value was wrong: https://github.com/llvm/llvm-project/issues/51941 (I should probably stop procrastinating sending a patch for that, now that I know what to do, it is trivial)

LogInit: Compiled with Clang: 10.0.1 (https://github.com/llvm/llvm-project ef32c611aa214dea855364efd7ba451ec5ec3f74)

Couple ways, for example on the github page [1] , click the "tags" link [2] above the file list, find the tag for release 14.0.0, which is llvmorg-14.0.0, and now you can do any commit operation with that name instead of a commit.

If you have a checkout, you can find the tag name by doing a git tag -l *14* and looking through the output; I'm intentionally providing a very general glob because one may not know beforehand their exact tag name conventions.

[1] https://github.com/llvm/llvm-project

[2] https://github.com/llvm/llvm-project/tags

clang (It is very similar to gcc, which many tutorials reccomend. You can get it here: https://github.com/llvm/llvm-project/releases/tag/llvmorg-14.0.0 [ see: LLVM-14.0.0-win64.exe ]

Interesting! What is your take on TinyGo. How does the LLVM compiler compare to say something you are familiar with, i.e. gcc? Would it be comparable?

Locating this kind of bug usually starts innocently, by commenting out various places of your own code, then analyzing your program under a debugger only to find yourself doing git clone https://github.com/llvm/llvm-project a few hours later 😅

> Should I report it somewhere?

Please do. You can open an issue (Bugzilla has been deprecated) on LLVM's github repo: https://github.com/llvm/llvm-project

Here is link number 1 - Previous text "Zig"

My default recommendation and preference is for Rust, but assuming that that doesn't work for you, I think you'd be best-served by Zig. It should meet all of your criteria and then some, with the only caveat is that it's still largely unstable and under churn. it still delivers on its promises far more consistently than V does, though

zig has chosen to list its system dependencies like this, basically declaring what is required & its min version. you could include this in your repo's README.md file

Also very excited to hear more folks push behind the macOS cross-compilation story. :) I think Andrew and Jakub plan to add tbd framework stubs that would in theory enable linking against macOS frameworks without actually having a copy of the SDK.

How to read the standard library source code

Zig https://ziglang.org/

Zig doesn't have a stable ABI and has various features that are not C-like. By default, its structs/enums/etc are not compatible with C ABI, but it can be selectively opt-in. There is a proposal to define a Zig ABI, but the resolution is unclear.

Rust is trying to be there. D Language is there. Zig is around there. Nim is around there. V lang maybe.