From: Link Mauve <linkmauve@linkmauve.fr>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: "Christophe Leroy (CS GROUP)" <chleroy@kernel.org>,
"Mukesh Kumar Chaurasiya (IBM)" <mkchauras@gmail.com>,
linkmauve@linkmauve.fr, ojeda@kernel.org, boqun.feng@gmail.com,
gary@garyguo.net, bjorn3_gh@protonmail.com, lossin@kernel.org,
a.hindborg@kernel.org, aliceryhl@google.com, tmgross@umich.edu,
dakr@kernel.org, corbet@lwn.net, maddy@linux.ibm.com,
mpe@ellerman.id.au, npiggin@gmail.com, 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 V4 2/3] rust: Add PowerPC support
Date: Tue, 10 Feb 2026 10:42:11 +0100 [thread overview]
Message-ID: <aYr9c90CWAXZ3AVl@luna> (raw)
In-Reply-To: <CANiq72nkVmE_91yz82e1cRuJK8F9SPP5GpD1mT=NYLBbRTL8OQ@mail.gmail.com>
Hi,
On Mon, Feb 09, 2026 at 01:48:01PM +0100, Miguel Ojeda wrote:
> On Mon, Feb 9, 2026 at 1:29 PM Christophe Leroy (CS GROUP)
> <chleroy@kernel.org> wrote:
> >
> > As far as I understand the patch is complete, the problem is outside the
> > kernel, it is in the libcore provided by rust or the rust compiler.
> >
> > That libcore seems to call __udivdi3() and __umoddi3() which are not
> > provided by the kernel. Instead if should call the functions do_div()
> > and friends provided by include/asm-generic/div64.h, or provide
> > __udivdi3() and __umoddi3() on its own.
>
> Yeah, but what I mean is, should we add this if it doesn't link,
> especially without a note or comment of some kind? (Perhaps to your
> tracking issue in GitHub?)
>
> i.e. if I understand correctly, you prefer to not add the panicking
> intrinsics to `rust/compiler_builtins.rs`, which I agree isn't ideal.
> By the way, it would be nice if IBM could join one of the meetings
> with have with upstream Rust to raise this topic again with them.
I’m just an unemployed contributor, with no ties to any of that but
sheer interest, would it be ok for me to join that call as well? I am
interested in resolving that issue in core, only three types have that
issue and only in their formatting code so far.
>
> In any case, it is up to you, of course. My only concern on the Rust
> bits is on the docs side, the rest looks fine.
>
> Thanks!
>
> Cheers,
> Miguel
>
--
Link Mauve
next prev parent reply other threads:[~2026-02-10 9:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-09 10:54 [PATCH V4 0/3] Rust support for powerpc Mukesh Kumar Chaurasiya (IBM)
2026-02-09 10:54 ` [PATCH V4 1/3] powerpc/jump_label: adjust inline asm to be consistent Mukesh Kumar Chaurasiya (IBM)
2026-02-09 10:54 ` [PATCH V4 2/3] rust: Add PowerPC support Mukesh Kumar Chaurasiya (IBM)
2026-02-09 12:02 ` Miguel Ojeda
2026-02-09 12:29 ` Christophe Leroy (CS GROUP)
2026-02-09 12:48 ` Miguel Ojeda
2026-02-10 5:27 ` Mukesh Kumar Chaurasiya
2026-02-10 9:17 ` Miguel Ojeda
2026-02-10 9:42 ` Link Mauve [this message]
2026-02-10 9:53 ` Miguel Ojeda
2026-02-10 5:11 ` kernel test robot
2026-02-09 10:54 ` [PATCH V4 3/3] powerpc: Enable Rust for ppc64le Mukesh Kumar Chaurasiya (IBM)
2026-02-09 11:52 ` Miguel Ojeda
2026-02-10 5:29 ` 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=aYr9c90CWAXZ3AVl@luna \
--to=linkmauve@linkmauve.fr \
--cc=a.hindborg@kernel.org \
--cc=aliceryhl@google.com \
--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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox