From: Daniel Gomez <da.gomez@kernel.org>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: Andreas Hindborg <a.hindborg@kernel.org>,
Matthew Wilcox <willy@infradead.org>,
linux-mm@kvack.org, lsf-pc@lists.linux-foundation.org,
Alice Ryhl <aliceryhl@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
gost.dev@samsung.com, Greg KH <gregkh@linuxfoundation.org>,
Julia Lawall <julia.lawall@inria.fr>,
Kairui Song <kasong@tencent.com>,
Luis Chamberlain <mcgrof@kernel.org>,
Miguel Ojeda <ojeda@kernel.org>,
rust-for-linux@vger.kernel.org,
Tamir Duberstein <tamird@gmail.com>
Subject: Re: [LSF/MM/BPF TOPIC] Evaluating Rust for XArray
Date: Wed, 18 Feb 2026 12:24:00 +0100 [thread overview]
Message-ID: <aZWfP-LyMvDsHVnz@macos> (raw)
In-Reply-To: <CANiq72naQfG=nSiPJdCXgqM1M_7ynDE5Stt-jiBGPqS9pipQtw@mail.gmail.com>
On 2026-02-17 21:18, Miguel Ojeda wrote:
> On Tue, Feb 17, 2026 at 6:51 PM Andreas Hindborg <a.hindborg@kernel.org> wrote:
> >
> > We don't have to wait 5-10 years for gcc to fully support Rust, before
> > we start playing with this.
>
> By the way, I don't think we will need that many years to use GCC if
> companies are interested on it and support projects like GCC Rust
> and/or `rustc_codegen_gcc`, given their current state (for context,
> the latter is able to boot a kernel with Rust enabled for x86_64, and
> the former is prioritizing Rust for Linux).
>
> Let me use this opportunity to say: if anyone wants to support that
> work, e.g. hardware companies for their architecture, then please ping
> me and I am happy to help getting in touch with them and figuring
> funding and things like that.
I'm not aware of the official GCC roadmap but LWN covered it in
"predictions for the new year" article [1]. Quoting:
"The gccrs project will deliver a working Rust compiler this year; it
will be usable to build the kernel's Rust code. This ambitious project
...
The availability of a GCC-based compiler will make that transition
easier for many people, especially those working with architectures that
the LLVM-based rustc compiler does not support..."
Link: https://lwn.net/Articles/1052269/ [1]
Whether that becomes true or not should not be relevant for the
discussion, as stated in this thread.
next prev parent reply other threads:[~2026-02-18 11:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-17 14:28 [LSF/MM/BPF TOPIC] Evaluating Rust for XArray Daniel Gomez
2026-02-17 14:41 ` Matthew Wilcox
2026-02-17 17:51 ` Andreas Hindborg
2026-02-17 20:14 ` Miguel Ojeda
2026-02-18 8:47 ` Andreas Hindborg
2026-02-17 20:18 ` Miguel Ojeda
2026-02-18 11:24 ` Daniel Gomez [this message]
2026-02-17 14:44 ` Tamir Duberstein
2026-02-17 18:57 ` Andreas Hindborg
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=aZWfP-LyMvDsHVnz@macos \
--to=da.gomez@kernel.org \
--cc=a.hindborg@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=aliceryhl@google.com \
--cc=gost.dev@samsung.com \
--cc=gregkh@linuxfoundation.org \
--cc=julia.lawall@inria.fr \
--cc=kasong@tencent.com \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=mcgrof@kernel.org \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=ojeda@kernel.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tamird@gmail.com \
--cc=willy@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.