| ... | @@ -76,23 +76,15 @@ This produces a `zig2` executable in the current working directory. This is a | ... | @@ -76,23 +76,15 @@ This produces a `zig2` executable in the current working directory. This is a |
| 76 | [without LLVM extensions](https://github.com/ziglang/zig/issues/16270), and is | 76 | [without LLVM extensions](https://github.com/ziglang/zig/issues/16270), and is |
| 77 | therefore lacking these features: | 77 | therefore lacking these features: |
| 78 | - Release mode optimizations | 78 | - Release mode optimizations |
| 79 | - [aarch64 machine code backend](https://github.com/ziglang/zig/issues/21172) | | |
| 80 | - [@cImport](https://github.com/ziglang/zig/issues/20630) | | |
| 81 | - [zig translate-c](https://github.com/ziglang/zig/issues/20875) | | |
| 82 | - [Ability to compile assembly files](https://github.com/ziglang/zig/issues/21169) | | |
| 83 | - [Some ELF linking features](https://github.com/ziglang/zig/issues/17749) | 79 | - [Some ELF linking features](https://github.com/ziglang/zig/issues/17749) |
| 84 | - [Most COFF/PE linking features](https://github.com/ziglang/zig/issues/17751) | 80 | - [Some COFF/PE linking features](https://github.com/ziglang/zig/issues/17751) |
| 85 | - [Some WebAssembly linking features](https://github.com/ziglang/zig/issues/17750) | 81 | - [Some WebAssembly linking features](https://github.com/ziglang/zig/issues/17750) |
| 86 | - [Ability to create import libs from def files](https://github.com/ziglang/zig/issues/17807) | | |
| 87 | - [Ability to create static archives from object files](https://github.com/ziglang/zig/issues/9828) | 82 | - [Ability to create static archives from object files](https://github.com/ziglang/zig/issues/9828) |
| | 83 | - [Ability to compile assembly files](https://github.com/ziglang/zig/issues/21169) |
| 88 | - Ability to compile C, C++, Objective-C, and Objective-C++ files | 84 | - Ability to compile C, C++, Objective-C, and Objective-C++ files |
| 89 | | 85 | |
| 90 | However, a compiler built this way does provide a C backend, which may be | 86 | Even when built this way, Zig provides an LLVM backend that produces bitcode |
| 91 | useful for creating system packages of Zig projects using the system C | 87 | files, which may be optimized and compiled into object files via a system Clang |
| 92 | toolchain. **In this case, LLVM is not needed!** | | |
| 93 | | | |
| 94 | Furthermore, a compiler built this way provides an LLVM backend that produces | | |
| 95 | bitcode files, which may be compiled into object files via a system Clang | | |
| 96 | package. This can be used to produce system packages of Zig applications | 88 | package. This can be used to produce system packages of Zig applications |
| 97 | without the Zig package dependency on LLVM. | 89 | without the Zig package dependency on LLVM. |
| 98 | | 90 | |