{"slug": "gccrs", "name": "gccrs", "category": "dev-libs", "category_name": "Libraries and frameworks", "description": "", "recommenders": 3, "commenters": 5, "warners": 0, "score": 3.002, "rising": -0.98, "first": "2025-11-18", "latest": "2026-07-03", "why": "It is fully self-hosting and can be built from source.", "why_is_quote": true, "has_verdict": false, "sentiment": {"recommend": 3, "neutral": 1, "compare": 1, "warn": 0}, "spark": [1, 0, 0, 1, 0, 0, 0, 0, 1, 0, 0, 0], "listed": true, "loved": [], "caveat": "", "short_quote": "It is fully self-hosting and can be built from source.", "kind": "", "icon": true, "domain": null, "github_repo": "github.com/rust-gcc/gccrs", "official_url": "https://rust-gcc.github.io/", "pricing": "", "aliases": ["gccrs"], "verdict": null, "praise": [{"label": "", "summary": "", "quotes": [{"id": 780433760, "item_id": 48777110, "url": "https://news.ycombinator.com/item?id=48777110", "by": "xvilka", "date": "2026-07-03", "version": null, "stance": "recommend", "quote": "For this, gcc-rs[1][2] is the most promising candidate.", "excerpt": "> compiling Rust programs for platforms not supported by LLVM For this, gcc-rs[1][2] is the most promising candidate. [1] https://rust-gcc.github.io/ [2] https://github.com/Rust-GCC/gccrs", "context": "", "use_case": "Rust compiler via GCC", "switched_from": "", "story": "crustc: entirety of `rustc`, translated to C"}, {"id": 750115745, "item_id": 46882234, "url": "https://news.ycombinator.com/item?id=46882234", "by": "LeFantome", "date": "2026-02-03", "version": null, "stance": "recommend", "quote": "It is fully self-hosting and can be built from source.", "excerpt": "> There are many architectures that NetBSD supports where Rust is not available Are there many architectures that NetBSD supports where GCC is not available? The rustc_codegen_gcc project allows using the rustc compiler to target any architecture that GCC supports. I think it is pretty far along. https://github.com/rust-lang/rustc_codegen_gcc > getting a Rust compiler running in the first place is hard > bootstrap re", "context": "", "use_case": "", "switched_from": "", "story": "Rust in the NetBSD Kernel, and other odd decisions"}, {"id": 735520097, "item_id": 45970006, "url": "https://news.ycombinator.com/item?id=45970006", "by": "aw1621107", "date": "2025-11-18", "version": null, "stance": "recommend", "quote": "whenever gccrs comes online that will be yet another defensive layer", "excerpt": "> and rustc could include malicious code that isn\u2019t obvious to an outside auditor. I believe mrustc [0] is generally considered the current defense against a trusting trust attack, and IIRC it has verified the lack of such an attack up to rustc 1.74, which is the latest version it currently supports. Presumably whenever gccrs comes online that will be yet another defensive layer. [0]: https://github.com/thepowersgang", "context": "", "use_case": "", "switched_from": "", "story": "Pre-PEP: Rust for CPython"}]}], "caveats": [], "who": [], "tags": [], "use_cases": ["rust compiler via gcc"], "compared": [{"slug": "rustc-codegen-gcc", "name": "rustc_codegen_gcc", "co": 2, "switched_from": 0, "switched_to": 0}], "makers": [], "threads": [{"url": "https://news.ycombinator.com/item?id=48768464", "title": "crustc: entirety of `rustc`, translated to C", "mentions": 2}, {"url": "https://news.ycombinator.com/item?id=46866042", "title": "Rust in the NetBSD Kernel, and other odd decisions", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=46178442", "title": "Eurydice: a Rust to C compiler", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=45955319", "title": "Pre-PEP: Rust for CPython", "mentions": 1}], "sentiment_by_month": {"2025-11": {"recommend": 1}, "2025-12": {"neutral": 1}, "2026-01": {}, "2026-02": {"recommend": 1}, "2026-03": {}, "2026-04": {}, "2026-05": {}, "2026-06": {}, "2026-07": {"recommend": 1, "compare": 1}, "2026-08": {}, "2026-09": {}, "2026-10": {}}, "versions": [], "version_unnamed": 0, "family_ref": null, "runs_on": null, "lines": [], "quotes": [{"id": 780489568, "item_id": 48780598, "url": "https://news.ycombinator.com/item?id=48780598", "by": "moltonel", "date": "2026-07-03", "version": null, "stance": "compare", "quote": "Gccrs is valuable for various reasons", "excerpt": "Gccrs is valuable for various reasons (bootstrapping, refining the spec, etc), but for the main purpose of \"compiling to targets supported by gcc but not llvm\", it's definitely not as promising as https://github.com/rust-lang/rustc_codegen_gcc. It's a rustc backend, at the same level as llvm or cranelift, it's much further along than gccrs (already available as a rustup component and can compile any rust code) and wi", "context": "", "use_case": "", "switched_from": "", "story": "crustc: entirety of `rustc`, translated to C"}, {"id": 780433760, "item_id": 48777110, "url": "https://news.ycombinator.com/item?id=48777110", "by": "xvilka", "date": "2026-07-03", "version": null, "stance": "recommend", "quote": "For this, gcc-rs[1][2] is the most promising candidate.", "excerpt": "> compiling Rust programs for platforms not supported by LLVM For this, gcc-rs[1][2] is the most promising candidate. [1] https://rust-gcc.github.io/ [2] https://github.com/Rust-GCC/gccrs", "context": "", "use_case": "Rust compiler via GCC", "switched_from": "", "story": "crustc: entirety of `rustc`, translated to C"}, {"id": 750115745, "item_id": 46882234, "url": "https://news.ycombinator.com/item?id=46882234", "by": "LeFantome", "date": "2026-02-03", "version": null, "stance": "recommend", "quote": "It is fully self-hosting and can be built from source.", "excerpt": "> There are many architectures that NetBSD supports where Rust is not available Are there many architectures that NetBSD supports where GCC is not available? The rustc_codegen_gcc project allows using the rustc compiler to target any architecture that GCC supports. I think it is pretty far along. https://github.com/rust-lang/rustc_codegen_gcc > getting a Rust compiler running in the first place is hard > bootstrap re", "context": "", "use_case": "", "switched_from": "", "story": "Rust in the NetBSD Kernel, and other odd decisions"}, {"id": 738887840, "item_id": 46180490, "url": "https://news.ycombinator.com/item?id=46180490", "by": "Y_Y", "date": "2025-12-07", "version": null, "stance": "neutral", "quote": "There's a Rust compiler in C++ in case that's any good to you", "excerpt": "https://github.com/Rust-GCC/gccrs/tree/master/gcc/rust There's a Rust compiler in C++ in case that's any good to you", "context": "", "use_case": "", "switched_from": "", "story": "Eurydice: a Rust to C compiler"}, {"id": 735520097, "item_id": 45970006, "url": "https://news.ycombinator.com/item?id=45970006", "by": "aw1621107", "date": "2025-11-18", "version": null, "stance": "recommend", "quote": "whenever gccrs comes online that will be yet another defensive layer", "excerpt": "> and rustc could include malicious code that isn\u2019t obvious to an outside auditor. I believe mrustc [0] is generally considered the current defense against a trusting trust attack, and IIRC it has verified the lack of such an attack up to rustc 1.74, which is the latest version it currently supports. Presumably whenever gccrs comes online that will be yet another defensive layer. [0]: https://github.com/thepowersgang", "context": "", "use_case": "", "switched_from": "", "story": "Pre-PEP: Rust for CPython"}]}