> Does this mean that y'all are open to the self-hosted compiler supporting CPU architectures unlikely to ever have LLVM support? Yes! We won't block 1.0 on th

> Does this mean that y'all are open to the self-hosted compiler supporting CPU architectures unlikely to ever have LLVM support? Yes! We won't block 1.0 on the quality of the less mainstream targets, but that's what the tier system is for - to ship a compiler that has varying levels of quality for various targets, while communicating clearly to users what kind of experience they can expect for each one. SuperH patches are absolutely welcome. > how is zig cc anticipated to work with a self-hosted Zig? Will there be a dependency on clang [...]? The main distribution of Zig will be LLVM/Clang-enabled. However it is already possible to build a version of Zig that does not have these features enabled. In such case, compiling C, C++, and Objective-C code will result in an error. However, the arocc project[1] is emerging, which, depending on a combination of how much funding ZSF gets and how much enthusiasm the unpaid contributors working in their spare time have, is looking like a promising C frontend that would be available even without LLVM/Clang. It is C only, however, with no intention of compiling C++ or Objective-C. > would zig cc support the planned C backend? As it is currently implemented: no. Zig invokes clang to turn C source code into object files. However, with the arocc frontend mentioned above, this would be converting the C source code into ZIR (or perhaps AIR), which could then be lowered with any of the backends, including the (partially complete) C backend. In such case, the C output would look drastically different than the input. It would look more like a machine-generated IR than natural C code that a human would write. [1]: https://github.com/Vexu/arocc https://github.com/Vexu/arocc