rust-snapshot:add riscv64 toolchains
PATCH 1/1 rust-snapshot:add riscv64 toolchains
From: Chen Pei <[email protected]>
--- meta/recipes-devtools/rust/rust-snapshot.inc | 4 ++++ 1 file changed, 4 insertions(+)
meta/recipes-devtools/rust/rust-snapshot.inc +4 -0
@@ -21,6 +21,10 @@ SRC_URI[rust-std-snapshot-powerpc64le.sha256sum] = "ef697469b2a3ea8897f49b70e3be SRC_URI[rustc-snapshot-powerpc64le.sha256sum] = "11630fc51fffe722e52f649357b5948c24b5305cfb61a8114527234e054451c4" SRC_URI[cargo-snapshot-powerpc64le.sha256sum] = "ba7188b2c7890e61bf58d3aa9e94c323fec375f67cf03841bbcc0f6c800fe6ad" +SRC_URI[rust-std-snapshot-riscv64gc.sha256sum] = "284b09a96d4cdbb96827914a318f9c41e2b207c0afeae76b9f0e3830d2ef2d4d" +SRC_URI[rustc-snapshot-riscv64gc.sha256sum] = "5f3e69a185c7246773948ac97c053cf135d81ffdbf926d10a3339de93424f26b" +SRC_URI[cargo-snapshot-riscv64gc.sha256sum] = "b94e262dec82b7cacf3baa77f35601c82d389ad338d118b42da4d23e26240760" + SRC_URI += " \ https://static.rust-lang.org/dist/${RUST_STD_SNAPSHOT}.tar.xz;name=rust-std-snapshot-${RUST_BUILD_ARCH};subdir=rust-snapshot-components \ https://static.rust-lang.org/dist/${RUSTC_SNAPSHOT}.tar.xz;name=rustc-snapshot-${RUST_BUILD_ARCH};subdir=rust-snapshot-components \
Signature · 1 line
2.25.1
I do have to ask, what kind of hardware are you using? Riscv64 systems tend to be seen as something akin to raspberry pi, but if building rust (which takes at least ten minutes on a 2x64 core x86 server) is now feasible, I'd like to know how :)
Alex
Quoted 35 lines · On Sat, 19 Nov 2022 at 11:11, cp0613 <[email protected]> wrote:
From: Chen Pei <[email protected]>
Signed-off-by Chen Pei <[email protected]>--- meta/recipes-devtools/rust/rust-snapshot.inc | 4 ++++ 1 file changed, 4 insertions(+)meta/recipes-devtools/rust/rust-snapshot.inc +4
-1@@ -21,6 +21,10 @@ SRC_URI[rust-std-snapshot-powerpc64le.sha256sum] = "ef697469b2a3ea8897f49b70e3be SRC_URI[rustc-snapshot-powerpc64le.sha256sum] = "11630fc51fffe722e52f649357b5948c24b5305cfb61a8114527234e054451c4" SRC_URI[cargo-snapshot-powerpc64le.sha256sum] = "ba7188b2c7890e61bf58d3aa9e94c323fec375f67cf03841bbcc0f6c800fe6ad" +SRC_URI[rust-std-snapshot-riscv64gc.sha256sum] = "284b09a96d4cdbb96827914a318f9c41e2b207c0afeae76b9f0e3830d2ef2d4d" +SRC_URI[rustc-snapshot-riscv64gc.sha256sum] = "5f3e69a185c7246773948ac97c053cf135d81ffdbf926d10a3339de93424f26b" +SRC_URI[cargo-snapshot-riscv64gc.sha256sum] = "b94e262dec82b7cacf3baa77f35601c82d389ad338d118b42da4d23e26240760" + SRC_URI += " \ https://static.rust-lang.org/dist/${RUST_STD_SNAPSHOT}.tar.xz;name=rust-std-snapshot-${RUST_BUILD_ARCH};subdir=rust-snapshot-components \ https://static.rust-lang.org/dist/${RUSTC_SNAPSHOT}.tar.xz;name=rustc-snapshot-${RUST_BUILD_ARCH};subdir=rust-snapshot-components \ --2.25.1
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#173513): https://lists.openembedded.org/g/openembedded-core/message/173513
Mute This Topic: https://lists.openembedded.org/mt/95130600/1686489
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
I am using a high performance riscv64 SOC TH1520, an example of the Wujian 600’s platform released by T-Head. You can find more information from:
https://riscv.org/blog/2022/08/alibaba-cloud-unveils-chip-development-platform-to-support-developers-with-risc-v-based-high-performance-socs-alibaba-cloud/
Thanks.
Right, but are you actually running bitbake on this board, which according to the page has only 4 cores? And if you do, what targets are you building and how long do they take?
Otherwise I am not sure what riscv rust-snapshot is useful for. It would help if you explain the use case.
Alex
Quoted 13 lines · On Sat, 19 Nov 2022 at 13:51, cp0613 <[email protected]> wrote:
I am using a high performance riscv64 SOC TH1520, an example of the Wujian 600’s platform released by T-Head. You can find more information from:
https://riscv.org/blog/2022/08/alibaba-cloud-unveils-chip-development-platform-to-support-developers-with-risc-v-based-high-performance-socs-alibaba-cloud/
Thanks.-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#173516): https://lists.openembedded.org/g/openembedded-core/message/173516
Mute This Topic: https://lists.openembedded.org/mt/95130600/1686489
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
Yes, now bitbake is running on this board.
The example TH1520 is 4cores, but Wujian 600 supports more cores.
It does take a lot of time to run on this board now, and I don’t see the actual significance at the moment, but I think this is part of the riscv ecology and will play a role in the near future. Thanks.
Yes, but this needs to be of practical use, and not just an experiment that you ran. I'd rather defer this until there is for example a broadly available cloud resource where you can run bitbake and get completion times similar to that of established architectures. Keep in mind that someone has to update those checksums with each rust upgrade for example. And test that things work and do not regress.
Alex
Quoted 14 lines · On Mon, 21 Nov 2022 at 02:40, cp0613 <[email protected]> wrote:
Yes, now bitbake is running on this board.
The example TH1520 is 4cores, but Wujian 600 supports more cores.
It does take a lot of time to run on this board now, and I don’t see the actual significance at the moment, but I think this is part of the riscv ecology and will play a role in the near future. Thanks.-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#173644): https://lists.openembedded.org/g/openembedded-core/message/173644
Mute This Topic: https://lists.openembedded.org/mt/95130600/1686489
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
Yes, I agree with your point of view and understand the impact of this, the current time may not be mature enough,
thanks for your review.