[PATCH v4 2/2] arm64: rust: Enable Rust support for AArch64

[Pratham Patel]

On Tue, 24 Oct 2023 at 20:49, Miguel Ojeda
<miguel.ojeda.sandonis at gmail.com> wrote:
> > but from a developer's and packager's
> > perspective, this will lead to a few wasted hours until the
> > metaphorical person figures out why said Rust code failed to build for
> > AArch64 BE.
>
> Why would the code fail to build? i.e. as far as I understand, Boqun
> successfully compiled and QEMU-booted a BE image.
>
> If you mean that it could stop compiling at any point because it is
> not officially supported, then note that we pin the compiler, and that
> it also applies to the rest of the code due to other unstable features
> too, which is why we need to get the Rust project to support the
> kernel properly for the use cases we need (not just targets, but also
> features).

Yes, apologies for not clarifying it. I meant exactly that: the code
would stop compiling if either the target was dropped for any reason,
or supporting AArch64 BE would hold back upgrading the compiler for
other architectures. Though, this is from a very high level overview.
If you feel like this won't be an issue, I don't have any problems
with this :)

> Also please note that, even if everything else was formally supported,
> it would still be a good idea to add this support early (possibly with
> a warning or gate or similar if not intended to be used by end users
> yet) so that we have the first big-endian target around.


> > P.S. This is my first time sending an email to a mailing list, sorry
> > if I mucked something up.
>
> The content looks fine :)
>
> However, I think the proper `In-Reply-To` header is not there so Lore
> gets confused -- did you use the suggested parameters at the bottom of
> e.g. [1]?
>
> [1] https://lore.kernel.org/rust-for-linux/CAM+6MoE1DyOay-fMWQP0hsenz174hSuGJnKM7symh0C-y1mqZw@mail.gmail.com/

Yes, I appear to have missed copying the `In-Reply-To` header in this
reply thread. Sorry about that.