From: Alice Ryhl <aliceryhl@google.com>
To: Mukesh Kumar Chaurasiya <mkchauras@gmail.com>
Cc: Miguel Ojeda <miguel.ojeda.sandonis@gmail.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: [PATCH V6 2/3] rust: Add PowerPC support
Date: Mon, 23 Feb 2026 09:22:33 +0000 [thread overview]
Message-ID: <aZwcWfYkBnivrgNa@google.com> (raw)
In-Reply-To: <aZu6cSqnvO91w1m4@li-1a3e774c-28e4-11b2-a85c-acc9f2883e29.ibm.com>
On Mon, Feb 23, 2026 at 07:56:02AM +0530, Mukesh Kumar Chaurasiya wrote:
> On Sun, Feb 22, 2026 at 08:11:17PM +0100, Miguel Ojeda wrote:
> > On Sun, Feb 22, 2026 at 8:07 PM Link Mauve <linkmauve@linkmauve.fr> wrote:
> > >
> > > Should we come back to describing the target like I did in my first
> > > patch[1] in scripts/generate_rust_target.rs, or should I bring that to
> > > Rust to create a powerpc-unknown-unknown-softfloat target upstream? Or
> > > is there a better third solution I’m not thinking of?
> >
> > We are trying to stop using the custom target specs, so we should ask
> > upstream to give you a built-in target you can use (or equivalently, a
> > flag to do what you need, but I think the idea is to not have such a
> > flag).
> >
> > i.e. even if you used the custom target JSON, we would still need to
> > ask, since the goal is to remove that script entirely.
>
> I think, disabling altivec, fpu and vsx with compiler flag will work.
>
> What are your opinion on this?
I think you can and should submit a PR to add a softfloat target to
upstream Rust right now, and I believe there should be no issue in
accepting that.
If there's a workaround we can use on existing compiler versions without
the target, that's great too, but we should get the target in upstream
asap.
Alice
next prev parent reply other threads:[~2026-02-23 9:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-10 9:00 [PATCH V6 0/3] Rust support for powerpc Mukesh Kumar Chaurasiya (IBM)
2026-02-10 9:00 ` [PATCH V6 1/3] powerpc/jump_label: adjust inline asm to be consistent Mukesh Kumar Chaurasiya (IBM)
2026-02-10 9:00 ` [PATCH V6 2/3] rust: Add PowerPC support Mukesh Kumar Chaurasiya (IBM)
2026-02-22 18:09 ` Alice Ryhl
2026-02-22 19:07 ` Link Mauve
2026-02-22 19:11 ` Miguel Ojeda
2026-02-23 2:21 ` Mukesh Kumar Chaurasiya
2026-02-23 2:26 ` Mukesh Kumar Chaurasiya
2026-02-23 9:22 ` Alice Ryhl [this message]
2026-02-24 4:57 ` Mukesh Kumar Chaurasiya
2026-02-23 15:31 ` Miguel Ojeda
2026-02-24 4:59 ` Mukesh Kumar Chaurasiya
2026-02-24 8:58 ` Ralf Jung
2026-03-02 5:55 ` Mukesh Kumar Chaurasiya
2026-03-02 7:29 ` Alice Ryhl
2026-03-02 12:28 ` Ralf Jung
2026-02-10 9:00 ` [PATCH V6 3/3] powerpc: Enable Rust for ppc64le Mukesh Kumar Chaurasiya (IBM)
2026-03-25 8:29 ` [PATCH V6 0/3] Rust support for powerpc Madhavan Srinivasan
2026-03-26 22:16 ` 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=aZwcWfYkBnivrgNa@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=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=miguel.ojeda.sandonis@gmail.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 \
/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.