From: Christian Schrefl <chrisi.schrefl@gmail.com>
To: Rudraksha Gupta <guptarud@gmail.com>,
stable@vger.kernel.org, regressions@lists.linux.dev,
rust-for-linux@vger.kernel.org, Miguel Ojeda <ojeda@kernel.org>,
llvm@lists.linux.dev,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Cc: "Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Andreas Hindborg" <a.hindborg@kernel.org>,
"Alice Ryhl" <aliceryhl@google.com>,
"Danilo Krummrich" <dakr@kernel.org>,
"Trevor Gross" <tmgross@umich.edu>,
"Benno Lossin" <lossin@kernel.org>
Subject: Re: ARMv7 Linux + Rust doesn't boot when compiling with only LLVM=1
Date: Tue, 16 Dec 2025 15:41:52 +0100 [thread overview]
Message-ID: <0705db10-3cbb-4958-a116-112457f9af6c@gmail.com> (raw)
In-Reply-To: <1286af8e-f908-45db-af7c-d9c5d592abfd@gmail.com>
On 12/14/25 12:54 AM, Rudraksha Gupta wrote:
> Hello all,
>
>
> I have the following problem: https://gitlab.postmarketos.org/postmarketOS/pmbootstrap/-/issues/2635
>
>
> In short, what is happening is the following:
>
>
> - The kernel boots and outputs via UART when I build the kernel with the following:
>
> make LLVM=1 ARCH="$arm" CC="${CC:-gcc}"
>
>
> - The kernel doesn't boot and there is no output via UART when I build the kernel with the following:
>
> make LLVM=1 ARCH="$arm"
>
>
> The only difference being: CC="${CC:-gcc}". Is this expected? I think this was present in the Linux kernel ever since Rust was enabled for ARMv7, and I never encountered it because postmarketOS was originally building the first way.
I've managed to the get the build setup for qemu-armv7. For some reason
I could not get past the initrd even on kernels that are supposed to work,
but I think that is unrelated (and not a kernel issue).
On the linux-next kernel I didn't get any output on the console from qemu so I
think I've reproduced the issue. Changing CONFIG_RUST=n did not change the behavior.
So I this is almost certainly a LLVM/clang issue and not a Rust issue. I'll try to
do a bit more digging, but I'm not sure how much I'll get done.
Adding the LLVM and ARM lists to this conversation.
Cheers,
Christian
next prev parent reply other threads:[~2025-12-16 14:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-13 23:54 ARMv7 Linux + Rust doesn't boot when compiling with only LLVM=1 Rudraksha Gupta
2025-12-14 6:06 ` Miguel Ojeda
2025-12-14 7:34 ` Rudraksha Gupta
2025-12-15 11:19 ` Gary Guo
2025-12-17 10:01 ` Rudraksha Gupta
2025-12-15 12:17 ` Christian Schrefl
2025-12-17 10:10 ` Rudraksha Gupta
2025-12-16 14:41 ` Christian Schrefl [this message]
2025-12-17 10:21 ` Rudraksha Gupta
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=0705db10-3cbb-4958-a116-112457f9af6c@gmail.com \
--to=chrisi.schrefl@gmail.com \
--cc=a.hindborg@kernel.org \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=dakr@kernel.org \
--cc=gary@garyguo.net \
--cc=guptarud@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=llvm@lists.linux.dev \
--cc=lossin@kernel.org \
--cc=ojeda@kernel.org \
--cc=regressions@lists.linux.dev \
--cc=rust-for-linux@vger.kernel.org \
--cc=stable@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;
as well as URLs for NNTP newsgroup(s).