4 ms·
It’s a huge project, I wonder if it wouldn’t be simpler to try to compile cranelift or mrustc to wasm (that’s still quite difficult) then use wasm2c to get a bo
by iTokio 2y ago
It’s a huge project, I wonder if it wouldn’t be simpler to try to compile cranelift or mrustc to wasm (that’s still quite difficult) then use wasm2c to get a bootstrap compiler.
- School-Cotton 2y agoThe resulting C would not be “source code”. Edit to explain further: the point is for the code to be written (or at least auditable) by humans.
- ncruces 2y agoAs long both rust-to-wasm (or zig-to-wasm) and wasm2c are auditable, and every step reproducible, why do you need the generated C to be auditable?
- School-Cotton 2y agoThe point is to shorten the minimal bootstrap path to Rust. With your suggestion you can't use rust until after you already have rust-to-wasm transpiler available (which almost certainly itself already requires rust, so you are back where you started).
- ludocode 2y agoThe generated C code could contain a backdoor. Generated C is not really auditable so there would be no way to tell that the code is compromised.
- pabs3 2y agoThe article mentions that the Bootstrappable Builds folks don't allow pre-generated code in their processes, they always have to build or bootstrap it from the real source.
- fallingsquirrel 2y agoThat's the approach Zig is taking: https://ziglang.org/news/goodbye-cpp/ https://ziglang.org/news/goodbye-cpp/