apache / apache/teaclave-trustzone-sdk
Upstream status for rustc aarch64-unknown-optee-trustzone target?
- Dominant language
- Rust
- Stars
- 284
- Forks
- 83
- Avg merge
- 3h 34m
- Merged PRs (30d)
- 6
Description
I observe that `aarch64-unknown-optee-trustzone` target is maintained here [1]. Are there any plans to make it an official target upstream? I do see another target: `aarch64-unknown-teeos` became officially supported tier 3 target upstream here [2] [3] [4] [5]. Can we re-purpose that target for OP-TEE? Or we need to add another target upstream?
[1] https://github.com/mesalock-linux/rust/commits/teaclave-trustzone-sdk-1.56.1
[2] https://github.com/rust-lang/rust/blob/master/src/doc/rustc/src/platform-support/aarch64-unknown-teeos.md
[3] https://github.com/rust-lang/rust/pull/113480
[4] https://github.com/rust-lang/libc/pull/3333
[5] https://github.com/rust-lang/rust/pull/116565
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with rustc's src/doc/rustc/src/platform-support/aarch64-unknown-teeos.md and review the linked rustc and libc pull requests. Compare that upstream target with the maintained aarch64-unknown-optee-trustzone branch, then determine whether repurposing the existing target or proposing a new one is appropriate. Done means an agreed upstream path is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers, embedded-iot
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 18/100