https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93090
--- Comment #2 from John Paul Adrian Glaubitz <glaubitz at physik dot fu-berlin.de> --- (In reply to Jakub Jelinek from comment #1) > The Go FE actually isn't that independent, the same gofrontend is used by > both GCC and LLVM, the same FE written in C++ in that case has then a > compiler dependent layer for GCC and another one for LLVM. Right. I think this argument was partially true though for earlier implementations of the Go frontend in GCC, wasn't it? > So, is for the bountysource another interface for the rustc FE ok, or are > you looking for completely independent FE implementation? I'm fine with either way actually. My main motivation is to have a Rust compiler that supports more architectures than the one currently developed by the Rust develeopers. > And even if yes, can e.g. the runtime library be shared with rustc, > or does it need to be independent? If I understand the approach by "sapir" correctly, this is actually what's being worked on in his gcc-rust frontend: > https://github.com/sapir/gcc-rust/tree/rust > Again, talking about Go, I think the go runtime is shared by all of goland, > gcc-go and gollvm. Which would be perfectly fine with me. I didn't want to leave the impression that a completely independent implementation would be necessary. I just mentioned it because it was brought up as one of the arguments for having a Rust frondend in GCC within the community. I think the approach by "sapir" is actually very promising as it should be able to keep up with Rust upstream which is currently a rather fast moving target.