From: Conor Dooley <conor.dooley@microchip.com>
To: <linux-riscv@lists.infradead.org>
Cc: conor@kernel.org, "Miguel Ojeda" <ojeda@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Wedson Almeida Filho" <wedsonaf@gmail.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Jonathan Corbet" <corbet@lwn.net>,
"Paul Walmsley" <paul.walmsley@sifive.com>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Nathan Chancellor" <nathan@kernel.org>,
"Nick Desaulniers" <ndesaulniers@google.com>,
"Tom Rix" <trix@redhat.com>,
rust-for-linux@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, llvm@lists.linux.dev
Subject: Re: [PATCH v1 0/2] RISC-V: enable rust
Date: Thu, 8 Jun 2023 08:01:16 +0100 [thread overview]
Message-ID: <20230608-dispatch-sneer-aa09bd7b2eb8@wendy> (raw)
In-Reply-To: <20230307102441.94417-1-conor.dooley@microchip.com>
[-- Attachment #1: Type: text/plain, Size: 1095 bytes --]
Hey Kwang,
On 08/06/2023 05:46, 손광훈/Tizen Platform Lab(SR)/삼성전자 wrote:
> Hi,
> Recently I'm trying to put a rust patch on the risc-v board.
> I saw a patch [1] and looked through it roughly.
> Only if llvm(not gcc) is allowed, it looks good with no major problems.
>
> > I'll revisit this when my thoughts have settled down.
>
> If you let me know the problematic part, may I try the patch?
>
> [1] https://lore.kernel.org/linux-riscv/20230405-itinerary-handgrip-
> a5ffba368148@spud/
Yeah, you can definitely try this or the downstream rust-for-linux
project - both should work well on RISC-V.
The problematic part is figuring out what ISA extensions are supported
by the rust compiler being used (and by bindgen), and deciding what to
put in -march as a result.
I think it is unlikely to matter for you, unless you're aggressively
mixing versions for different parts of your toolchain.
I do intend revisting this, probably after the min. version for rust
gets bumped, I've just been really busy with other work the last weeks.
Cheers,
Conor.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Conor Dooley <conor.dooley@microchip.com>
To: <linux-riscv@lists.infradead.org>
Cc: conor@kernel.org, "Miguel Ojeda" <ojeda@kernel.org>,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Wedson Almeida Filho" <wedsonaf@gmail.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Jonathan Corbet" <corbet@lwn.net>,
"Paul Walmsley" <paul.walmsley@sifive.com>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Nathan Chancellor" <nathan@kernel.org>,
"Nick Desaulniers" <ndesaulniers@google.com>,
"Tom Rix" <trix@redhat.com>,
rust-for-linux@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, llvm@lists.linux.dev
Subject: Re: [PATCH v1 0/2] RISC-V: enable rust
Date: Thu, 8 Jun 2023 08:01:16 +0100 [thread overview]
Message-ID: <20230608-dispatch-sneer-aa09bd7b2eb8@wendy> (raw)
In-Reply-To: <20230307102441.94417-1-conor.dooley@microchip.com>
[-- Attachment #1.1: Type: text/plain, Size: 1095 bytes --]
Hey Kwang,
On 08/06/2023 05:46, 손광훈/Tizen Platform Lab(SR)/삼성전자 wrote:
> Hi,
> Recently I'm trying to put a rust patch on the risc-v board.
> I saw a patch [1] and looked through it roughly.
> Only if llvm(not gcc) is allowed, it looks good with no major problems.
>
> > I'll revisit this when my thoughts have settled down.
>
> If you let me know the problematic part, may I try the patch?
>
> [1] https://lore.kernel.org/linux-riscv/20230405-itinerary-handgrip-
> a5ffba368148@spud/
Yeah, you can definitely try this or the downstream rust-for-linux
project - both should work well on RISC-V.
The problematic part is figuring out what ISA extensions are supported
by the rust compiler being used (and by bindgen), and deciding what to
put in -march as a result.
I think it is unlikely to matter for you, unless you're aggressively
mixing versions for different parts of your toolchain.
I do intend revisting this, probably after the min. version for rust
gets bumped, I've just been really busy with other work the last weeks.
Cheers,
Conor.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
[-- Attachment #2: Type: text/plain, Size: 161 bytes --]
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2023-06-08 7:02 UTC|newest]
Thread overview: 81+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-07 10:24 [PATCH v1 0/2] RISC-V: enable rust Conor Dooley
2023-03-07 10:24 ` Conor Dooley
2023-03-07 10:24 ` [PATCH v1 1/2] scripts: generate_rust_target: enable building on RISC-V Conor Dooley
2023-03-07 10:24 ` Conor Dooley
2023-03-07 11:21 ` Miguel Ojeda
2023-03-07 11:21 ` Miguel Ojeda
2023-03-07 10:24 ` [PATCH v1 2/2] RISC-V: enable building 64-bit kernels with rust support Conor Dooley
2023-03-07 10:24 ` Conor Dooley
2023-03-07 10:56 ` Miguel Ojeda
2023-03-07 10:56 ` Miguel Ojeda
2023-03-07 11:01 ` Conor Dooley
2023-03-07 11:01 ` Conor Dooley
2023-03-07 11:56 ` Miguel Ojeda
2023-03-07 11:56 ` Miguel Ojeda
2023-03-07 12:51 ` Conor Dooley
2023-03-07 12:51 ` Conor Dooley
2023-03-07 11:07 ` [PATCH v1 0/2] RISC-V: enable rust Miguel Ojeda
2023-03-07 11:07 ` Miguel Ojeda
2023-03-30 8:23 ` Conor Dooley
2023-03-30 8:23 ` Conor Dooley
2023-03-30 9:11 ` Conor Dooley
2023-03-30 9:11 ` Conor Dooley
2023-04-03 16:35 ` Miguel Ojeda
2023-04-03 16:35 ` Miguel Ojeda
2023-04-03 17:14 ` Conor Dooley
2023-04-03 17:14 ` Conor Dooley
2023-04-05 21:18 ` Conor Dooley
2023-04-05 21:18 ` Conor Dooley
2023-04-03 16:32 ` Miguel Ojeda
2023-04-03 16:32 ` Miguel Ojeda
2023-06-08 7:01 ` Conor Dooley [this message]
2023-06-08 7:01 ` Conor Dooley
2023-06-08 7:10 ` Conor Dooley
2023-06-08 7:10 ` Conor Dooley
2023-06-08 7:50 ` Kwanghoon Son
2023-06-08 7:50 ` Kwanghoon Son
2023-06-08 7:50 ` Kwanghoon Son
2023-06-08 11:52 ` Miguel Ojeda
2023-06-08 11:52 ` Miguel Ojeda
2023-06-08 12:28 ` Conor Dooley
2023-06-08 12:28 ` Conor Dooley
2024-01-17 11:30 ` Conor Dooley
2024-01-17 11:30 ` Conor Dooley
2024-01-17 18:23 ` Miguel Ojeda
2024-01-17 18:23 ` Miguel Ojeda
2024-01-18 15:49 ` Conor Dooley
2024-01-18 15:49 ` Conor Dooley
2024-01-18 16:09 ` Miguel Ojeda
2024-01-18 16:09 ` Miguel Ojeda
2024-01-25 12:30 ` Conor Dooley
2024-01-25 12:30 ` Conor Dooley
2024-01-25 12:50 ` Miguel Ojeda
2024-01-25 12:50 ` Miguel Ojeda
2024-01-25 13:45 ` Conor Dooley
2024-01-25 13:45 ` Conor Dooley
2024-01-26 21:00 ` Miguel Ojeda
2024-01-26 21:00 ` Miguel Ojeda
2024-01-26 22:00 ` Conor Dooley
2024-01-26 22:00 ` Conor Dooley
2024-01-27 13:46 ` Miguel Ojeda
2024-01-27 13:46 ` Miguel Ojeda
2024-02-09 15:18 ` Conor Dooley
2024-02-09 15:18 ` Conor Dooley
2024-02-10 8:13 ` Trevor Gross
2024-02-10 8:13 ` Trevor Gross
2024-02-12 19:03 ` Ramon de C Valle
2024-02-12 19:03 ` Ramon de C Valle
2024-02-12 20:36 ` Sami Tolvanen
2024-02-12 20:36 ` Sami Tolvanen
2024-02-13 20:08 ` Ramon de C Valle
2024-02-13 20:08 ` Ramon de C Valle
2024-02-14 3:14 ` Trevor Gross
2024-02-14 3:14 ` Trevor Gross
[not found] ` <CAOcBZORDaHHH3jTL3GO7OsDubhhyQE0Uy2uAjJpiRzrKBgqaOw@mail.gmail.com>
2024-02-12 19:11 ` Miguel Ojeda
2024-02-12 19:11 ` Miguel Ojeda
2024-02-12 20:17 ` Conor Dooley
2024-02-12 20:17 ` Conor Dooley
2024-02-12 20:37 ` Conor Dooley
2024-02-12 20:37 ` Conor Dooley
2024-02-13 20:09 ` Ramon de C Valle
2024-02-13 20:09 ` Ramon de C Valle
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=20230608-dispatch-sneer-aa09bd7b2eb8@wendy \
--to=conor.dooley@microchip.com \
--cc=alex.gaynor@gmail.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=conor@kernel.org \
--cc=corbet@lwn.net \
--cc=gary@garyguo.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=llvm@lists.linux.dev \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=ojeda@kernel.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=rust-for-linux@vger.kernel.org \
--cc=trix@redhat.com \
--cc=wedsonaf@gmail.com \
/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.