From: <rsbecker@nexbridge•com>
To: "'Ezekiel Newren'" <ezekielnewren@gmail•com>
Cc: <CAH=ZcbCUL-rWw5E6p26T0039gs9q-P8iK5fp73-RzTzKiZ0zMQ@mail•gmail.com>,
<20250904-b4-pks-rust-breaking-change-v1-0-3af1d25e0be9@pks•im>,
<Johannes.Schindelin@gmx•de>, <ben.knoble@gmail•com>,
<cb@256bit•org>, <collin.funk1@gmail•com>, <contact@hacktivis•me>,
<eschwartz@gentoo•org>, <git@vger•kernel.org>,
<gitster@pobox•com>, <me@ttaylorr•com>, <newren@gmail•com>,
<phillip.wood123@gmail•com>, <pierre-emmanuel.patry@embecosm•com>,
<ps@pks•im>, <sam@gentoo•org>, <sandals@crustytoothpaste•net>
Subject: RE: [PATCH RFC 0/3] Introduce Rust and announce that it will become mandatorty
Date: Sat, 20 Sep 2025 19:17:50 -0400 [thread overview]
Message-ID: <002001dc2a84$cda40380$68ec0a80$@nexbridge.com> (raw)
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:
>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.
next prev parent reply other threads:[~2025-09-20 23:18 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-20 8:29 [PATCH RFC 0/3] Introduce Rust and announce that it will become mandatorty Sergey Fedorov
2025-09-20 18:39 ` rsbecker
2025-09-20 19:00 ` Ezekiel Newren
2025-09-20 19:25 ` Sam James
2025-09-20 23:17 ` rsbecker [this message]
2025-09-20 23:48 ` Ezekiel Newren
2025-09-21 1:15 ` rsbecker
2025-09-21 1:24 ` Ezekiel Newren
2025-09-21 3:18 ` rsbecker
2025-09-21 16:49 ` Ezekiel Newren
2025-09-21 23:07 ` rsbecker
2025-09-21 23:42 ` Ezekiel Newren
2025-09-22 16:21 ` rsbecker
-- strict thread matches above, loose matches on Subject: below --
2025-09-19 17:36 Sergey Fedorov
2025-09-19 17:56 ` Ezekiel Newren
2025-09-19 18:14 ` Collin Funk
2025-09-20 8:24 ` Florian Märkl
2025-09-22 15:59 ` Michael Orlitzky
2025-09-22 16:17 ` Sam James
2025-09-22 21:35 ` brian m. carlson
2025-09-22 21:47 ` Sam James
2025-09-23 5:05 ` Patrick Steinhardt
2025-09-22 23:23 ` Michael Orlitzky
2025-09-04 14:26 Patrick Steinhardt
2025-09-19 18:41 ` John Paul Adrian Glaubitz
2025-09-22 13:01 ` Patrick Steinhardt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='002001dc2a84$cda40380$68ec0a80$@nexbridge.com' \
--to=rsbecker@nexbridge$(echo .)com \
--cc=20250904-b4-pks-rust-breaking-change-v1-0-3af1d25e0be9@pks$(echo .)im \
--cc=CAH=ZcbCUL-rWw5E6p26T0039gs9q-P8iK5fp73-RzTzKiZ0zMQ@mail$(echo .)gmail.com \
--cc=Johannes.Schindelin@gmx$(echo .)de \
--cc=ben.knoble@gmail$(echo .)com \
--cc=cb@256bit$(echo .)org \
--cc=collin.funk1@gmail$(echo .)com \
--cc=contact@hacktivis$(echo .)me \
--cc=eschwartz@gentoo$(echo .)org \
--cc=ezekielnewren@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
--cc=me@ttaylorr$(echo .)com \
--cc=newren@gmail$(echo .)com \
--cc=phillip.wood123@gmail$(echo .)com \
--cc=pierre-emmanuel.patry@embecosm$(echo .)com \
--cc=ps@pks$(echo .)im \
--cc=sam@gentoo$(echo .)org \
--cc=sandals@crustytoothpaste$(echo .)net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox