zig-bootstrap
gccrs
zig-bootstrap | gccrs | |
---|---|---|
8 | 102 | |
332 | 2,264 | |
1.5% | 0.8% | |
7.1 | 10.0 | |
7 days ago | 8 days ago | |
C | ||
- | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
zig-bootstrap
-
Zig for Raspberry Pi 2 Model B
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.
-
Compiling Zig with Low RAM (16GB)?
Use Zig Bootstrap, it is easier. And It should work on 16gb.
-
compile zig based on llvm-14
you can cross compile for armv7a with zig-bootstrap
-
Zig is now self–hosted by default
They have a project for maintaining this: https://github.com/ziglang/zig-bootstrap
- Looking into Zig
-
[Discussion] I firmly believe a self hosted compiler is a huge security risk that *should not* be undertaken.
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.
-
Zig 0.8.0 Released!
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.
- Zig 0.8.0 Release Notes
gccrs
-
FreeBSD evaluating Rust's adoption into base system
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/
-
Why do lifetimes need to be leaky?
That's why gccrs doesn't even consider lifetime checking a part of the language (they plan to use Polonius, too).
- Rust-GCC: GCC Front-End for Rust
-
How hard would it be to port the Rust toolchain to a new non-POSIX OS written in Rust and get it to host its own development? What would that process entail?
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.
-
How hard is it to write a front end for a more complex language like Rust or Kotlin?
I recommend checking out the GCC Rust frontend project.
-
Rust contributions for Linux 6.4 are finally merged upstream!
That is what theyre refering to, yes. The GitHub is named https://github.com/Rust-GCC/gccrs
-
GCC 13 and the State of 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.
- Break rust Easter Egg Merged Into gccrs
-
Any alternate Rust compilers?
(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.)
-
Which programming languages, if all legacy code written in them was ported to a more modern language, would become extinct?
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)
What are some alternatives?
zig - General-purpose programming language and toolchain for maintaining robust, optimal, and reusable software.
gcc-rust - a (WIP) Rust frontend for gcc / a gcc backend for rustc
osxcross - Mac OS X cross toolchain for Linux, FreeBSD, OpenBSD and Android (Termux)
rustc_codegen_gcc - libgccjit AOT codegen for rustc
live-bootstrap - Use of a Linux initramfs to fully automate the bootstrapping process
rustc_codegen_gcc - libgccjit AOT codegen for rustc
MacOSX-SDKs - A collection of those pesky SDK folders: MacOSX10.1.5.sdk thru MacOSX11.3.sdk
mold - Mold: A Modern Linker 🦠
badger - Keyboard firmware written from scratch using Nim
rust - Empowering everyone to build reliable and efficient software.
tigerbeetle - A distributed financial accounting database designed for mission critical safety and performance. [Moved to: https://github.com/tigerbeetledb/tigerbeetle]
Rust-for-Linux - Adding support for the Rust language to the Linux kernel.