Recherches récentes
Options de recherche
@cbehopkins @dr2chase @jschauma It's the main compiler involved in the only reduced binary bootstrap seed project (https://guix.gnu.org/en/blog/2020/guix-further-reduces-bootstrap-seed-to-25/) I'm aware of.
As for Golang specifically, it weakens the Google domination, which I find valuable in itself.
Of course, making an interpreter instead of a GCC frontend & using that to compile a self-hosting compiler works too (you still need to compile that interpreter too at some point unless you write in assembler I guess, then you assemble it).
@cbehopkins @dr2chase @jschauma But then that begs the question, why make yet another compiler instead of reusing the optimization & portability work already done by others before you?
Having a compiler implemented in a safe language is a valid answer to that question, but it does mean you're willing to trade-off portability (or a lot more work to be done) in exchange for it.