[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <a6959bc0-f0bb-425b-b3b1-3123d3b809b5@app.fastmail.com>
Date: Wed, 04 Sep 2024 08:38:04 +0100
From: "Jiaxun Yang" <jiaxun.yang@...goat.com>
To: "Miguel Ojeda" <miguel.ojeda.sandonis@...il.com>
Cc: "Masahiro Yamada" <masahiroy@...nel.org>,
"Nathan Chancellor" <nathan@...nel.org>,
"Nicolas Schier" <nicolas@...sle.eu>,
"Richard Weinberger" <richard@....at>,
"Anton Ivanov" <anton.ivanov@...bridgegreys.com>,
"Johannes Berg" <johannes@...solutions.net>,
"Thomas Gleixner" <tglx@...utronix.de>, "Ingo Molnar" <mingo@...hat.com>,
"Borislav Petkov" <bp@...en8.de>,
"Dave Hansen" <dave.hansen@...ux.intel.com>, x86@...nel.org,
"H. Peter Anvin" <hpa@...or.com>, "Miguel Ojeda" <ojeda@...nel.org>,
"Alex Gaynor" <alex.gaynor@...il.com>,
"Wedson Almeida Filho" <wedsonaf@...il.com>,
"Boqun Feng" <boqun.feng@...il.com>, "Gary Guo" <gary@...yguo.net>,
Björn Roy Baron <bjorn3_gh@...tonmail.com>,
"Benno Lossin" <benno.lossin@...ton.me>,
"Andreas Hindborg" <a.hindborg@...sung.com>,
"Alice Ryhl" <aliceryhl@...gle.com>,
"Thomas Bogendoerfer" <tsbogend@...ha.franken.de>,
"Steven Rostedt" <rostedt@...dmis.org>,
"Masami Hiramatsu" <mhiramat@...nel.org>,
"Mark Rutland" <mark.rutland@....com>,
"Jonathan Corbet" <corbet@....net>, "Alex Shi" <alexs@...nel.org>,
"Yanteng Si" <siyanteng@...ngson.cn>,
"Nick Desaulniers" <ndesaulniers@...gle.com>,
"Bill Wendling" <morbo@...gle.com>,
"Justin Stitt" <justinstitt@...gle.com>, linux-kbuild@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-um@...ts.infradead.org,
rust-for-linux@...r.kernel.org,
"linux-mips@...r.kernel.org" <linux-mips@...r.kernel.org>,
linux-trace-kernel@...r.kernel.org, linux-doc@...r.kernel.org,
llvm@...ts.linux.dev
Subject: Re: [PATCH 3/3] rust: Enable for MIPS
在2024年9月3日九月 下午8:01,Miguel Ojeda写道:
> On Tue, Sep 3, 2024 at 8:32 PM Jiaxun Yang <jiaxun.yang@...goat.com> wrote:
>>
>> Ahh thanks for the elaboration.
>
> You're welcome!
>
>> However, kernel supports many ISA variants that are not defined by any rust target
>> triple, I'm not really sure if it's appropriate to define them all in upstream.
>
> They need to be in upstream Rust somehow, because upstream Rust does
> not want to stabilize `target.json` since it is too tied to LLVM (as
> far as we have been told). Whether that is via `-Ctarget-feature`, or a
> new `-Cglobal-target-feature`, or specific flags like `-Zfixed-x18`
> (originally `-Ctarget-feature=+reserve-x18`), or (many) new target
> triples for different combinations, or something else, it depends on
> the case and what upstream Rust wants to do.
>
> That is why we should tell them what is needed, ideally in a new issue
> in upstream Rust, and link it in
> https://github.com/Rust-for-Linux/linux/issues/355 (please see that
> list for similar examples).
Seems like this topic is covered by an existing issue
Reported at:
https://github.com/rust-embedded/wg/issues/792#issuecomment-2328133517
Thanks!
>
> I hope that explains a bit more the context.
>
> Cheers,
> Miguel
--
- Jiaxun
Powered by blists - more mailing lists