still not exactly sure what gcc-rs is trying to solve
Conversation
Notices
-
Jamie :blobcathearttrans: (jamie@crab.garden)'s status on Wednesday, 19-Apr-2023 12:34:29 CEST Jamie :blobcathearttrans:
-
.:Ninjatrappeur:. (ninjatrappeur@social.alternativebit.fr)'s status on Wednesday, 19-Apr-2023 12:34:26 CEST .:Ninjatrappeur:.
@bugaevc @jamie It'll also improve the bootstrap story. Rust is pretty tricky to bootstrap from the source ATM. Each compiler version relies on the previous one to build itself. The overall chain tend to be quite long*, GCC has a much better story in that area.
*llvm -> mrustc -> rustc 1.54 -> 55 -> 56 -> 57 -> 58 -> 59 -> 60 -> 61 -> 62 -> 63 -> 64 -> 65 -
Sergey Bugaev (bugaevc@floss.social)'s status on Wednesday, 19-Apr-2023 12:34:27 CEST Sergey Bugaev
@jamie supporting Rust inside the GCC? :)
Ekaitz Zárraga 👹 repeated this. -
Jamie :blobcathearttrans: (jamie@crab.garden)'s status on Wednesday, 19-Apr-2023 12:34:34 CEST Jamie :blobcathearttrans:
@Ninjatrappeur @bugaevc Oh wow I did not know that. That’s honestly terrifying and I’m glad they’re finding a way to avoid that
In conversation permalink Ekaitz Zárraga 👹 repeated this. -
Sergey Bugaev (bugaevc@floss.social)'s status on Wednesday, 19-Apr-2023 12:34:34 CEST Sergey Bugaev
@jamie @Ninjatrappeur see also
https://github.com/Rust-GCC/gccrs/wiki/Frequently-Asked-Questions#benefits
https://guix.gnu.org/en/blog/2018/bootstrapping-rust/But even without all that, it would still be a cool & awesome project, and a solid improvement to GCC.
In conversation permalink Attachments
-