RE: [PATCH RFC 0/3] Introduce Rust and announce that it will become mandatorty
- From
rsbecker@nexbridge.com <rsbecker@nexbridge.com>
- Date
- Sep 20, 2025, 23:17 UTC
- Message-ID
- <002001dc2a84$cda40380$68ec0a80$@nexbridge.com>
- In-Reply-To
- <CAH=ZcbDJR7gJ0tyQ-bk-n+Zid_csED74+X5OkTfbEiy5-_2R-w@mail.gmail.com>
On September 20, 2025 3:01 PM, Ezekiel Newren wrote:
Show 19 quoted lines
>On Sat, Sep 20, 2025 at 12:39 PM <rsbecker@nexbridge.com> wrote: >> To clarify, gcc is not available on all platforms. The overlap where >> gcc is supported and Rust is support is likely high, but more, where >> gcc is not supported then it is highly unlikely that Rust is >> supported. mrustc is a difficult more that requires gcc even if that >> is not clearly stated - it does not build with c17, for example. This >> double requirement is making the probability of being able to continue >> to support git even less for me on NonStop. My team is working hard to >> push Rust availability and we realize that gccrs is an easier path, >> but those two are currently outside of our control because of complexities in the >loader on NonStop. > >Is there a C compiler that works on NonStop and Linux? I ask because I'm >wondering if code from gccrs could help with augmenting that compiler. From what >I understand gccrs is written in C++17, but Rust's native approach uses mrustc to >bootstrap, and then the rest of the Rust compiler is written in Rust. I don't have >$500,000 to spare for testing on real NonStop hardware, but if there was a C >compiler that worked on NonStop and Linux then there'd at least be the possibility >of people trying to make Rust work with it.
All I have is a C++17 compiler. gcc -std=c17 might work for compatibility on Linux but none of the gcc extensions work.