Skip to content

add riscv64im-unknown-openvm-elf tier 3 target#3

Draft
Tuanlinh12312 wants to merge 1 commit into
masterfrom
feat/riscv64im-unknown-openvm-elf
Draft

add riscv64im-unknown-openvm-elf tier 3 target#3
Tuanlinh12312 wants to merge 1 commit into
masterfrom
feat/riscv64im-unknown-openvm-elf

Conversation

@Tuanlinh12312
Copy link
Copy Markdown

Add riscv64im-unknown-openvm-elf as a tier 3 Rust target for the OpenVM zero-knowledge virtual machine (RV64IM ISA). The target includes std support via the OpenVM platform abstraction layer.

@shuklaayush shuklaayush force-pushed the feat/riscv64im-unknown-openvm-elf branch 3 times, most recently from 0edc748 to f1281db Compare May 13, 2026 18:45
@shuklaayush shuklaayush reopened this May 13, 2026
@shuklaayush shuklaayush requested a review from jonathanpwang May 13, 2026 19:08
@shuklaayush shuklaayush force-pushed the feat/riscv64im-unknown-openvm-elf branch 6 times, most recently from 22b86aa to 8f068e6 Compare May 13, 2026 22:21
@jonathanpwang
Copy link
Copy Markdown

Should we change the target to some openvm branch so we can merge it?
also any way to get CI to not break, or it has too many rust org stuff?

@shuklaayush shuklaayush force-pushed the feat/riscv64im-unknown-openvm-elf branch 2 times, most recently from d548e24 to ada9892 Compare May 14, 2026 05:25
Adds a new tier 3 target for the OpenVM zkVM, including its std/panic_abort
PAL modules, target spec, platform-support docs, bootstrap target-sanity
workaround, and build/release workflows for a custom toolchain.

Co-authored-by: Linh Nguyen <tuanlinh17032006@gmail.com>
@shuklaayush shuklaayush force-pushed the feat/riscv64im-unknown-openvm-elf branch from ada9892 to a5da1ed Compare May 14, 2026 09:14
@shuklaayush
Copy link
Copy Markdown

Should we change the target to some openvm branch so we can merge it?

can't we just close the pr after review and maintain the changes in the branch?

also any way to get CI to not break, or it has too many rust org stuff?

probably not, but the release workflow did work and we have a tarball
https://github.com/openvm-org/rust/releases/tag/openvm-nightly-2026-01-18

@jonathanpwang
Copy link
Copy Markdown

Should we change the target to some openvm branch so we can merge it?

can't we just close the pr after review and maintain the changes in the branch?

also any way to get CI to not break, or it has too many rust org stuff?

probably not, but the release workflow did work and we have a tarball https://github.com/openvm-org/rust/releases/tag/openvm-nightly-2026-01-18

We can, but given that this is a target we want to maintain, I'd just say we rename the branch to something more official

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants