git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH RFC 0/3] Introduce Rust and announce that it will become mandatorty

From
Sam James <sam@gentoo.org>
Date
Sep 20, 2025, 19:25 UTC
Message-ID
<87qzw10vv9.fsf@gentoo.org>
In-Reply-To
<CAH=ZcbDJR7gJ0tyQ-bk-n+Zid_csED74+X5OkTfbEiy5-_2R-w@mail.gmail.com>
Ezekiel Newren <ezekielnewren@gmail.com> writes:
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.
[Just some small technical notes, it doesn't need a reply.]

GCC defaults to C++17 but is written in C++14 (recently changed from C++11). I think the gccrs people may have talked about whether they can use C++17 to make some things easier (I suspect if they requested that, it would be approved, at least I'd support it and argue in favour).

mrustc isn't part of any official Rust bootstrap path, Rust upstream just use binaries. mrustc currently needs GCC for some trivial reasons (like hardcoding some workarounds for bugs w/ GCC-specific flags). I suspect it wouldn't be too hard to get it working with Clang. I don't know how many extensions it relies on in general that may be common but not in the standard.

But mrustc is written in C++, not C -- AFAIK NonStop has no C++ compiler.
Previous: Ezekiel NewrenNext: rsbecker@nexbridge.com
Message 4 of 13 in “Re: [PATCH RFC 0/3] Introduce Rust and announce that it will become mandatorty”
  1. Sergey FedorovSep 20, 2025
  2. rsbecker@nexbridge.comSep 20, 2025
  3. Ezekiel NewrenSep 20, 2025
  4. Sam JamesSep 20, 2025
  5. rsbecker@nexbridge.comSep 20, 2025
  6. Ezekiel NewrenSep 20, 2025
  7. rsbecker@nexbridge.comSep 21, 2025
  8. Ezekiel NewrenSep 21, 2025
  9. rsbecker@nexbridge.comSep 21, 2025
  10. Ezekiel NewrenSep 21, 2025
  11. rsbecker@nexbridge.comSep 21, 2025
  12. Ezekiel NewrenSep 21, 2025
  13. rsbecker@nexbridge.comSep 22, 2025

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.