From: Alice Ryhl <aliceryhl@google.com>
To: "J. Neuschäfer" <j.neuschaefer@gmx.net>
Cc: Mukesh Kumar Chaurasiya <mkchauras@gmail.com>,
Venkat Rao Bagalkote <venkat88@linux.ibm.com>,
Link Mauve <linkmauve@linkmauve.fr>,
ojeda@kernel.org, boqun.feng@gmail.com, gary@garyguo.net,
bjorn3_gh@protonmail.com, lossin@kernel.org,
a.hindborg@kernel.org, tmgross@umich.edu, dakr@kernel.org,
corbet@lwn.net, maddy@linux.ibm.com, mpe@ellerman.id.au,
npiggin@gmail.com, chleroy@kernel.org, peterz@infradead.org,
jpoimboe@kernel.org, jbaron@akamai.com, rostedt@goodmis.org,
ardb@kernel.org, rust-for-linux@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org
Subject: Re: Rust version requirement (was: [PATCH V2 3/3] powerpc: Enable Rust for ppc64le)
Date: Mon, 16 Feb 2026 11:29:05 +0000 [thread overview]
Message-ID: <aZL_gVBFVzMjQkYK@google.com> (raw)
In-Reply-To: <aZL-JO3950gc9YO_@probook>
On Mon, Feb 16, 2026 at 12:23:16PM +0100, J. Neuschäfer wrote:
> On Thu, Feb 05, 2026 at 09:12:01PM +0530, Mukesh Kumar Chaurasiya wrote:
> [...]
> > use rust version nightly-2026-01-28
> >
> > the latest one has some issue. I just raised a bug for the rustc
> > here[1].
> >
> > [1] https://github.com/rust-lang/rust/issues/152177
>
> Another reason to use a nightly version is that Rust inline assembly for
> PowerPC will only be stabilized[1] in version 1.94, so current release
> versions fail like this (tested with 1.91.1):
>
> error[E0658]: inline assembly is not stable yet on this architecture
> --> ../rust/kernel/sync/barrier.rs:19:14
> |
> 19 | unsafe { core::arch::asm!("") };
> | ^^^^^^^^^^^^^^^^^^^^
> |
> = note: see issue #93335 <https://github.com/rust-lang/rust/issues/93335> for more information
> = help: add `#![feature(asm_experimental_arch)]` to the crate attributes to enable
> = note: this compiler was built on 2025-11-07; consider upgrading it if it is out of date
>
> This is somewhat at odds with Documentation/process/changes.rst which
> only requires Rust 1.78. I wonder if the rust version requirement should
> generally be bumped, or if there should be arch-specific requirements
> somewhere in changes.rst or rust/arch-support.rst.
>
> Best regards,
> J. Neuschäfer
>
> [1]: https://github.com/rust-lang/rust/pull/147996
The MSRV is planned to be bumped to 1.85.
If it's available as a nightly feature on 1.78, then you can just add
#![feature(asm_experimental_arch)] to lib.rs, which already enables
several other stabilized feature on older compilers.
Otherwise powerpc support can always be gated to require a larger
rustc version than other platforms.
Alice
next prev parent reply other threads:[~2026-02-16 11:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-04 21:01 [PATCH V2 0/3] Rust support for powerpc Mukesh Kumar Chaurasiya (IBM)
2026-02-04 21:01 ` [PATCH V2 1/3] powerpc/jump_label: adjust inline asm to be consistent Mukesh Kumar Chaurasiya (IBM)
2026-02-05 8:09 ` Christophe Leroy (CS GROUP)
2026-02-05 8:24 ` Alice Ryhl
2026-02-04 21:01 ` [PATCH V2 2/3] rust: Add PowerPC support Mukesh Kumar Chaurasiya (IBM)
2026-02-04 21:01 ` [PATCH V2 3/3] powerpc: Enable Rust for ppc64le Mukesh Kumar Chaurasiya (IBM)
2026-02-05 8:14 ` Christophe Leroy (CS GROUP)
2026-02-05 13:52 ` Link Mauve
2026-02-05 14:51 ` Venkat Rao Bagalkote
2026-02-05 15:42 ` Mukesh Kumar Chaurasiya
2026-02-05 19:34 ` Miguel Ojeda
2026-02-05 20:02 ` Nathan Chancellor
2026-02-05 20:15 ` Miguel Ojeda
2026-02-11 22:23 ` Miguel Ojeda
2026-02-16 11:23 ` Rust version requirement (was: [PATCH V2 3/3] powerpc: Enable Rust for ppc64le) J. Neuschäfer
2026-02-16 11:29 ` Alice Ryhl [this message]
2026-02-05 15:45 ` [PATCH V2 3/3] powerpc: Enable Rust for ppc64le Mukesh Kumar Chaurasiya
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=aZL_gVBFVzMjQkYK@google.com \
--to=aliceryhl@google.com \
--cc=a.hindborg@kernel.org \
--cc=ardb@kernel.org \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=chleroy@kernel.org \
--cc=corbet@lwn.net \
--cc=dakr@kernel.org \
--cc=gary@garyguo.net \
--cc=j.neuschaefer@gmx.net \
--cc=jbaron@akamai.com \
--cc=jpoimboe@kernel.org \
--cc=linkmauve@linkmauve.fr \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=lossin@kernel.org \
--cc=maddy@linux.ibm.com \
--cc=mkchauras@gmail.com \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=ojeda@kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=rust-for-linux@vger.kernel.org \
--cc=tmgross@umich.edu \
--cc=venkat88@linux.ibm.com \
/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.