zig-bootstrap VS gccrs

if you know what compiler target is used on your pi 2 you can probably get someone to cross compile it for you. https://github.com/ziglang/zig-bootstrap This should be reasonably easy to use.

Use Zig Bootstrap, it is easier. And It should work on 16gb.

you can cross compile for armv7a with zig-bootstrap

They have a project for maintaining this: https://github.com/ziglang/zig-bootstrap

I think that's the purpose of the zig-bootstrap project. By having these dependencies installed: clang, llvm, python3, cmake (notice no zig) you end up with zig compiled.

The current state is that they offer a repo with LLVM and the stage1 (C++) compiler, which should build on any system that can build LLVM (so any system with a modern C++ compiler and build tools). Or you can grab the upstream Zig code and build it against regular LLVM 12 yourself using an existing LLVM 12 clang/etc stack.

There is a Rust front-end for GCC that is under active development [1]. If the chip vendors are not willing to develop and upstream a LLVM back-end then they can feel free to start contributing to it.

[1] https://rust-gcc.github.io/

That's why gccrs doesn't even consider lifetime checking a part of the language (they plan to use Polonius, too).

There's ongoing work on a Rust front-end for GCC (https://github.com/Rust-GCC/gccrs). Bit barebones right now -- ie, even core doesn't compile -- but there's funding, demand, and regular progress, so it'll only get better from there. Once gccrs can compile core, it should be ready to compile most of Rust, and thus if you've taught the calling conventions for C to GCC, you're golden.

I recommend checking out the GCC Rust frontend project.

That is what theyre refering to, yes. The GitHub is named https://github.com/Rust-GCC/gccrs

- But this misses so much extra context information

3. Macro invocations there are really subtle rules on how you treat macro invocations such as this which is not documented at all https://github.com/Rust-GCC/gccrs/blob/master/gcc/rust/expan...

Some day I personally want to write a blog post about how complicated and under spec'd Rust is, then write one about the stuff i do like it such as iterators being part of libcore so i don't need reactive extensions.

(Speaking of which, Rust-GCC (or gcc-rs or gccrs or whichever other of their names they decide is the primary one) isn't even going to be a complete C++ implementation. Their plan is to implement enough to compile Polonius (the NLL 2.0 borrow checker being developed in Rust for rustc) and then share that since borrow-checking isn't necessary for codegen... only to identify and reject invalid programs... making the C++ portion of it not that different in scope from mrustc.)

That bridge will be crossed with gccrs (compiling Rust with gcc directly, coming next month with GCC 13) and rust_codegen_gcc (rustc frontend, GCC backend, works now but just doesn’t yet have an “easy” setup)