Add `std` support for `armv7a-vex-v5` #145973

tropicaaal · 2025-08-28T22:13:29Z

This PR adds standard library support for the VEX V5 Brain (armv7a-vex-v5 target). It is more-or-less an updated version of the library-side work done in #131530.

This was a joint effort between me, @lewisfm, @max-niederman, @Gavin-Niederman and several other members of the vexide project.

Background

VEXos is a fairly unconventional operating system, with user code running in a restricted enviornment with regards to I/O capabilities and whatnot. As such, several OS-dependent APIs are unsupported or have partial support (such as std::net, std::process, and most of std::thread). A more comprehensive list of what does or doesn't work is outlined in the updated target documentation. Despite these limitations, we believe that libstd support on this target still has value to users, especially given the popular use of this hardware for educational purposes. For some previous discussion on this matter, see this comment.

SDK Linkage

VEXos doesn't really ship with an official libc or POSIX-style platform API (and though it does port newlib, these are stubbed on top of the underlying SDK). Instead, VEX provides their own SDK for calling platform APIs. Their official SDK is kept proprietary (with public headers), though open-source implementations exist. Following the precedent of the armv6k-nintendo-3ds team's work in #95897, we've opted not to directly link libstd to any SDK with the expectation that users will provide their own with one of the following options:

vex-sdk-download, which downloads an official proprietary SDK from VEX using a build script.
vex-sdk-jumptable, which is a compatible, open-source reimplementation of the SDK using firmware jumps.
vex-sdk-pros, which uses the PROS kernel as a provider for SDK functions.
Linking their own implementation or stubbing the functions required by libstd.

The vex-sdk crate used in the VEXos PAL provides libc-style FFI bindings for any compatible system library, so any of these options should work fine. A functional demo project using vex-sdk-download can be found here.

Future Work

This PR implements virtually everything we are currently able to implement given the current capabilities of the platform. The exception to this is file directory enumeration, though the implementation of that is sufficiently gross enough to drive us away from supporting this officially.

Additionally, I have a working branch implementing the panic_unwind runtime for this target, which is something that would be nice to see in the future, though given the volume of compiler changes i've deemed it out-of-scope for this PR.

rustbot · 2025-08-28T22:13:34Z

r? @tgross35

rustbot has assigned @tgross35.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.

Use r? to explicitly pick a reviewer

rustbot · 2025-08-28T22:13:38Z

Some changes occurred in src/doc/rustc/src/platform-support

cc @Noratrieb

These commits modify the library/Cargo.lock file. Unintentional changes to library/Cargo.lock can be introduced when switching branches and rebasing PRs.

If this was unintentional then you should revert the changes before this PR is merged.
Otherwise, you can ignore this comment.

These commits modify compiler targets.
(See the Target Tier Policy.)

The list of allowed third-party dependencies may have been modified! You must ensure that any new dependencies have compatible licenses before merging.

cc @davidtwco, @wesleywiser

library/std/src/sys/alloc/vexos.rs

library/std/src/sys/fs/vexos.rs

tgross35 · 2025-08-28T22:53:46Z

I think the limitations here seem fine, and from a quick skim nothing jumps out to me as problematic. Nominating to make sure the team doesn't have any concerns.

@rustbot label +I-libs-nominated

library/std/Cargo.toml

library/std/src/sys/alloc/vexos.rs

library/std/src/sys/fs/vexos.rs

library/std/src/sys/pal/vexos/mod.rs

library/std/src/sys/pal/vexos/time.rs

tgross35 · 2025-08-30T01:14:52Z

@rustbot author

rustbot · 2025-08-30T01:14:55Z

Reminder, once the PR becomes ready for a review, use @rustbot ready.

tropicaaal · 2025-08-30T02:47:53Z

@rustbot ready

tgross35 · 2025-08-30T03:00:48Z

Thanks for the updates here, I'll take a more thorough look through after the libs meeting (next Wednesday).

bors · 2025-09-03T18:49:56Z

☔ The latest upstream changes (presumably #146160) made this pull request unmergeable. Please resolve the merge conflicts.

rustbot · 2025-09-05T23:02:10Z

Some changes occurred in src/tools/cargo

cc @ehuss

tropicaaal · 2025-09-23T22:15:53Z

Hardware tests seem fine.

tgross35

Updates look great! Noticed one last nit on error messages.

Please squash, r=me after that and the error message change

View changes since this review

library/std/src/sys/fs/vexos.rs

tropicaaal · 2025-09-24T15:34:38Z

Done! Think things are in order (don't think I have permissions for bors r=). @tgross35

tgross35 · 2025-09-24T16:31:35Z

Code changes look good to me! But on a history nit, for the squashed commit it looks like you aren't listed as the author. Since you prepared the final state, you probably want to git commit --amend --reset-author to set youself as the author, then add @lewisfm back as a co-author (via Co-authored-by: Name <email> at the end of the commit message https://docs.github.com/en/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors).

Also you don't really need to keep all the squashed messages in the final commit message since they aren't relevant anymore. I know this is the default behavior for rebase s/squash, but by squash we really tend to mean f/fixup 🙂

Co-authored-by: Lewis McClelland <lewis@lewismcclelland.me>

tropicaaal · 2025-09-24T17:13:47Z

Code changes look good to me! But on a history nit, for the squashed commit it looks like you aren't listed as the author.

Yeah, I squashed everything into the first commit, which is why it ended up that way. I've fixed that issue and added lewis back as a co-author.

tgross35 · 2025-09-24T17:44:58Z

Looks great! Thanks for all the work here.

@bors r+

bors · 2025-09-24T17:45:01Z

📌 Commit b2634e3 has been approved by tgross35

It is now in the queue for this repository.

Add `std` support for `armv7a-vex-v5` This PR adds standard library support for the VEX V5 Brain (`armv7a-vex-v5` target). It is more-or-less an updated version of the library-side work done in rust-lang#131530. This was a joint effort between me, ``@lewisfm,`` ``@max-niederman,`` ``@Gavin-Niederman`` and several other members of the [`vexide` project](https://github.com/vexide/). ## Background VEXos is a fairly unconventional operating system, with user code running in a restricted enviornment with regards to I/O capabilities and whatnot. As such, several OS-dependent APIs are unsupported or have partial support (such as `std::net`, `std::process`, and most of `std::thread`). A more comprehensive list of what does or doesn't work is outlined in the [updated target documentation](https://github.com/vexide/rust/blob/vex-std/src/doc/rustc/src/platform-support/armv7a-vex-v5.md). Despite these limitations, we believe that `libstd` support on this target still has value to users, especially given the popular use of this hardware for educational purposes. For some previous discussion on this matter, see [this comment](rust-lang#131530 (comment)). ## SDK Linkage VEXos doesn't really ship with an official `libc` or POSIX-style platform API (and though it does port newlib, these are stubbed on top of the underlying SDK). Instead, VEX provides their own SDK for calling platform APIs. Their official SDK is kept proprietary (with public headers), though open-source implementations exist. Following the precedent of the `armv6k-nintendo-3ds` team's work in rust-lang#95897, we've opted not to directly link `libstd` to any SDK with the expectation that users will provide their own with one of the following options: - [`vex-sdk-download`](https://github.com/vexide/vex-sdk/tree/main/packages/vex-sdk-download), which downloads an official proprietary SDK from VEX using a build script. - [`vex-sdk-jumptable`](https://crates.io/crates/vex-sdk-jumptable), which is a compatible, open-source reimplementation of the SDK using firmware jumps. - [`vex-sdk-pros`](https://github.com/vexide/vex-sdk/tree/main/packages/vex-sdk-pros), which uses the [PROS kernel](https://github.com/purduesigbots/pros) as a provider for SDK functions. - Linking their own implementation or stubbing the functions required by libstd. The `vex-sdk` crate used in the VEXos PAL provides `libc`-style FFI bindings for any compatible system library, so any of these options *should* work fine. A functional demo project using `vex-sdk-download` can be found [here](https://github.com/vexide/armv7a-vex-v5-demo/tree/main). ## Future Work This PR implements virtually everything we are currently able to implement given the current capabilities of the platform. The exception to this is file directory enumeration, though the implementation of that is sufficiently [gross enough](https://github.com/vexide/vexide/blob/c6c5bad11e035cf4e51d429dca7e427210185ed4/packages/vexide-core/src/fs/mod.rs#L987) to drive us away from supporting this officially. Additionally, I have a working branch implementing the `panic_unwind` runtime for this target, which is something that would be nice to see in the future, though given the volume of compiler changes i've deemed it out-of-scope for this PR.

Rollup of 14 pull requests Successful merges: - #145067 (RawVecInner: add missing `unsafe` to unsafe fns) - #145277 (Do not materialise X in [X; 0] when X is unsizing a const) - #145973 (Add `std` support for `armv7a-vex-v5`) - #146667 (Add an attribute to check the number of lanes in a SIMD vector after monomorphization) - #146735 (unstably constify float mul_add methods) - #146737 (f16_f128: enable some more tests in Miri) - #146766 (Add attributes for #[global_allocator] functions) - #146905 (llvm: update remarks support on LLVM 22) - #146982 (Remove erroneous normalization step in `tests/run-make/linker-warning`) - #147005 (Small string formatting cleanup) - #147007 (Explicitly note `&[SocketAddr]` impl of `ToSocketAddrs`) - #147008 (bootstrap.py: Respect build.jobs while building bootstrap tool) - #147013 (rustdoc: Fix documentation for `--doctest-build-arg`) - #147015 (Use `LLVMDisposeTargetMachine`) r? `@ghost` `@rustbot` modify labels: rollup

Rollup merge of #145973 - vexide:vex-std, r=tgross35 Add `std` support for `armv7a-vex-v5` This PR adds standard library support for the VEX V5 Brain (`armv7a-vex-v5` target). It is more-or-less an updated version of the library-side work done in #131530. This was a joint effort between me, `@lewisfm,` `@max-niederman,` `@Gavin-Niederman` and several other members of the [`vexide` project](https://github.com/vexide/). ## Background VEXos is a fairly unconventional operating system, with user code running in a restricted enviornment with regards to I/O capabilities and whatnot. As such, several OS-dependent APIs are unsupported or have partial support (such as `std::net`, `std::process`, and most of `std::thread`). A more comprehensive list of what does or doesn't work is outlined in the [updated target documentation](https://github.com/vexide/rust/blob/vex-std/src/doc/rustc/src/platform-support/armv7a-vex-v5.md). Despite these limitations, we believe that `libstd` support on this target still has value to users, especially given the popular use of this hardware for educational purposes. For some previous discussion on this matter, see [this comment](#131530 (comment)). ## SDK Linkage VEXos doesn't really ship with an official `libc` or POSIX-style platform API (and though it does port newlib, these are stubbed on top of the underlying SDK). Instead, VEX provides their own SDK for calling platform APIs. Their official SDK is kept proprietary (with public headers), though open-source implementations exist. Following the precedent of the `armv6k-nintendo-3ds` team's work in #95897, we've opted not to directly link `libstd` to any SDK with the expectation that users will provide their own with one of the following options: - [`vex-sdk-download`](https://github.com/vexide/vex-sdk/tree/main/packages/vex-sdk-download), which downloads an official proprietary SDK from VEX using a build script. - [`vex-sdk-jumptable`](https://crates.io/crates/vex-sdk-jumptable), which is a compatible, open-source reimplementation of the SDK using firmware jumps. - [`vex-sdk-pros`](https://github.com/vexide/vex-sdk/tree/main/packages/vex-sdk-pros), which uses the [PROS kernel](https://github.com/purduesigbots/pros) as a provider for SDK functions. - Linking their own implementation or stubbing the functions required by libstd. The `vex-sdk` crate used in the VEXos PAL provides `libc`-style FFI bindings for any compatible system library, so any of these options *should* work fine. A functional demo project using `vex-sdk-download` can be found [here](https://github.com/vexide/armv7a-vex-v5-demo/tree/main). ## Future Work This PR implements virtually everything we are currently able to implement given the current capabilities of the platform. The exception to this is file directory enumeration, though the implementation of that is sufficiently [gross enough](https://github.com/vexide/vexide/blob/c6c5bad11e035cf4e51d429dca7e427210185ed4/packages/vexide-core/src/fs/mod.rs#L987) to drive us away from supporting this officially. Additionally, I have a working branch implementing the `panic_unwind` runtime for this target, which is something that would be nice to see in the future, though given the volume of compiler changes i've deemed it out-of-scope for this PR.

std: fix warning in VEXos stdio module Fixes building `std` on the `armv7a-vex-v5` target due to an unnecessarily mutable argument in `Stdin`. This was a stupid oversight on my part towards the end of rust-lang#145973's review process. Missed a warning and had a bad bootstrap config that didn't tell me about it when testing changes.

Rollup of 14 pull requests Successful merges: - rust-lang/rust#145067 (RawVecInner: add missing `unsafe` to unsafe fns) - rust-lang/rust#145277 (Do not materialise X in [X; 0] when X is unsizing a const) - rust-lang/rust#145973 (Add `std` support for `armv7a-vex-v5`) - rust-lang/rust#146667 (Add an attribute to check the number of lanes in a SIMD vector after monomorphization) - rust-lang/rust#146735 (unstably constify float mul_add methods) - rust-lang/rust#146737 (f16_f128: enable some more tests in Miri) - rust-lang/rust#146766 (Add attributes for #[global_allocator] functions) - rust-lang/rust#146905 (llvm: update remarks support on LLVM 22) - rust-lang/rust#146982 (Remove erroneous normalization step in `tests/run-make/linker-warning`) - rust-lang/rust#147005 (Small string formatting cleanup) - rust-lang/rust#147007 (Explicitly note `&[SocketAddr]` impl of `ToSocketAddrs`) - rust-lang/rust#147008 (bootstrap.py: Respect build.jobs while building bootstrap tool) - rust-lang/rust#147013 (rustdoc: Fix documentation for `--doctest-build-arg`) - rust-lang/rust#147015 (Use `LLVMDisposeTargetMachine`) r? `@ghost` `@rustbot` modify labels: rollup

Rollup merge of #147049 - vexide:vex-std, r=workingjubilee std: fix warning in VEXos stdio module Fixes building `std` on the `armv7a-vex-v5` target due to an unnecessarily mutable argument in `Stdin`. This was a stupid oversight on my part towards the end of #145973's review process. Missed a warning and had a bad bootstrap config that didn't tell me about it when testing changes.

Add `std` support for `armv7a-vex-v5` This PR adds standard library support for the VEX V5 Brain (`armv7a-vex-v5` target). It is more-or-less an updated version of the library-side work done in rust-lang#131530. This was a joint effort between me, `@lewisfm,` `@max-niederman,` `@Gavin-Niederman` and several other members of the [`vexide` project](https://github.com/vexide/). ## Background VEXos is a fairly unconventional operating system, with user code running in a restricted enviornment with regards to I/O capabilities and whatnot. As such, several OS-dependent APIs are unsupported or have partial support (such as `std::net`, `std::process`, and most of `std::thread`). A more comprehensive list of what does or doesn't work is outlined in the [updated target documentation](https://github.com/vexide/rust/blob/vex-std/src/doc/rustc/src/platform-support/armv7a-vex-v5.md). Despite these limitations, we believe that `libstd` support on this target still has value to users, especially given the popular use of this hardware for educational purposes. For some previous discussion on this matter, see [this comment](rust-lang#131530 (comment)). ## SDK Linkage VEXos doesn't really ship with an official `libc` or POSIX-style platform API (and though it does port newlib, these are stubbed on top of the underlying SDK). Instead, VEX provides their own SDK for calling platform APIs. Their official SDK is kept proprietary (with public headers), though open-source implementations exist. Following the precedent of the `armv6k-nintendo-3ds` team's work in rust-lang#95897, we've opted not to directly link `libstd` to any SDK with the expectation that users will provide their own with one of the following options: - [`vex-sdk-download`](https://github.com/vexide/vex-sdk/tree/main/packages/vex-sdk-download), which downloads an official proprietary SDK from VEX using a build script. - [`vex-sdk-jumptable`](https://crates.io/crates/vex-sdk-jumptable), which is a compatible, open-source reimplementation of the SDK using firmware jumps. - [`vex-sdk-pros`](https://github.com/vexide/vex-sdk/tree/main/packages/vex-sdk-pros), which uses the [PROS kernel](https://github.com/purduesigbots/pros) as a provider for SDK functions. - Linking their own implementation or stubbing the functions required by libstd. The `vex-sdk` crate used in the VEXos PAL provides `libc`-style FFI bindings for any compatible system library, so any of these options *should* work fine. A functional demo project using `vex-sdk-download` can be found [here](https://github.com/vexide/armv7a-vex-v5-demo/tree/main). ## Future Work This PR implements virtually everything we are currently able to implement given the current capabilities of the platform. The exception to this is file directory enumeration, though the implementation of that is sufficiently [gross enough](https://github.com/vexide/vexide/blob/c6c5bad11e035cf4e51d429dca7e427210185ed4/packages/vexide-core/src/fs/mod.rs#L987) to drive us away from supporting this officially. Additionally, I have a working branch implementing the `panic_unwind` runtime for this target, which is something that would be nice to see in the future, though given the volume of compiler changes i've deemed it out-of-scope for this PR.

Rollup of 14 pull requests Successful merges: - rust-lang#145067 (RawVecInner: add missing `unsafe` to unsafe fns) - rust-lang#145277 (Do not materialise X in [X; 0] when X is unsizing a const) - rust-lang#145973 (Add `std` support for `armv7a-vex-v5`) - rust-lang#146667 (Add an attribute to check the number of lanes in a SIMD vector after monomorphization) - rust-lang#146735 (unstably constify float mul_add methods) - rust-lang#146737 (f16_f128: enable some more tests in Miri) - rust-lang#146766 (Add attributes for #[global_allocator] functions) - rust-lang#146905 (llvm: update remarks support on LLVM 22) - rust-lang#146982 (Remove erroneous normalization step in `tests/run-make/linker-warning`) - rust-lang#147005 (Small string formatting cleanup) - rust-lang#147007 (Explicitly note `&[SocketAddr]` impl of `ToSocketAddrs`) - rust-lang#147008 (bootstrap.py: Respect build.jobs while building bootstrap tool) - rust-lang#147013 (rustdoc: Fix documentation for `--doctest-build-arg`) - rust-lang#147015 (Use `LLVMDisposeTargetMachine`) r? `@ghost` `@rustbot` modify labels: rollup

std: fix warning in VEXos stdio module Fixes building `std` on the `armv7a-vex-v5` target due to an unnecessarily mutable argument in `Stdin`. This was a stupid oversight on my part towards the end of rust-lang#145973's review process. Missed a warning and had a bad bootstrap config that didn't tell me about it when testing changes.

This PR reorganizes vexide's internal codebase in preparation for rust-lang/rust#145973. Testing this branch currently requires the `nightly-2025-09-26` toolchain or newer, as well as a `cargo-v5` installation built from [this branch](https://github.com/vexide/cargo-v5/tree/upstreamed-target). Things are still pretty messy - some docs and tests and whatnot need updating. Closes #352, #354, #358, and #334. ## Relevant Work - Rust fork: https://github.com/vexide/rust/tree/vex-std - Website: - vexide/website#29 - ~~https://github.com/vexide/website/compare/v0.8-upgrade-guide~~ (merged into former) - cargo-v5: vexide/cargo-v5#30 - vex-v5-serial refactor: vexide/vex-v5-serial#9 - vex-sdk refactors: https://github.com/vexide/vex-sdk - vexide-template: vexide/vexide-template#14 ## The Big Changes - `vexide` now uses rustc's `armv7a-vex-v5` target, rather than our own custom target spec. This involves a new linkerscript that augments the one in rustc to faciliate the differential upload patcher. - Most of `vexide-core` has been gutted, including `fs`, most of `time`, `io`, `float`, `path`, and anything else that's now in `std`. - The `program` module in core has been repurposed to contain `CodeSignature`-related types (previously located in `vexide-startup`). - Added a `code_signature` function for reading the currently running program's code signature. - Added a `linked_file` function as a safe wrapper over `vexSystemLinkAddrGet()`. - `vexide-panic` is gone. Custom panic behavior is now done through a panic hook optionally registered by `vexide-startup` rather than our own `#[panic_handler]`. - `vexide-async` and `vexide-startup` are now dependent on `std`, with `vexide-devices` being optionally dependent (allowing for `std::io::{Read, Write}` implementations). The remaining subcrates remain `no_std`-compatible. - `vexide-async` was made `std`-dependent so that we can use libstd's `Instant` type for public APIs such as `sleep_until`. - `vexide-startup` was made `std`-dependent because it expects several things to be setup by the Rust runtime now, and also uses `std::io` for the patcher (which replaces `vexide_core::io`). It also has to call `println!` to do banner stuff. - An SDK provider can now be configured by choosing one of the following "backends" as feature flags (which vexide-startup will handle via the new `vex-sdk-*` family of crates): - `vex-sdk-download`: Downloads and links the official `libv5rt.a` using a build script. - `vex-sdk-jumptable`: What you're used to. - `vex-sdk-mock`: A stubbed version of the SDK that will be useful later for doing unit tests and running vexide on host targets. - `vex-sdk-pros`: Uses the partner SDK in libpros as a provider by bridging API incompatibilities between libv5rt and libv5rts. - `talc` is still used as our allocator by default, since it's lighter and theoretically faster in most cases than `dlmalloc`. The allocator APIs have been moved to `vexide-startup`. - `no_std_io` dependence is gone now that we have `std::io`. We now optionally support `embedded-io` implementations in `vexide-devices` through a feature flag if the user wants to use `vexide-devices` in a `#[no_std]` environment still. <img width="240" alt="merendas" src="https://github.com/user-attachments/assets/bb5630be-6ce5-49e9-a8df-1a1b7624b905" />

rustbot assigned tgross35 Aug 28, 2025

lewisfm suggested changes Aug 28, 2025

View reviewed changes

library/std/src/sys/alloc/vexos.rs Show resolved Hide resolved

library/std/src/sys/fs/vexos.rs Outdated Show resolved Hide resolved

library/std/src/sys/fs/vexos.rs Outdated Show resolved Hide resolved

rustbot added the I-libs-nominated Nominated for discussion during a libs team meeting. label Aug 28, 2025

This comment has been minimized.

Sign in to view

tgross35 reviewed Aug 28, 2025

View reviewed changes

library/std/Cargo.toml Show resolved Hide resolved

tgross35 reviewed Aug 30, 2025

View reviewed changes

rustbot removed the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Aug 30, 2025

rustbot added the S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. label Aug 30, 2025

rustbot added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. and removed S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. labels Aug 30, 2025

tgross35 added S-waiting-on-team DEPRECATED: Use the team-based variants `S-waiting-on-t-lang`, `S-waiting-on-t-compiler`, ... and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Aug 30, 2025

tropicaaal force-pushed the vex-std branch from 3288184 to 09ab298 Compare September 3, 2025 20:37

This comment has been minimized.

Sign in to view

tropicaaal force-pushed the vex-std branch from 09ab298 to 2796a03 Compare September 5, 2025 23:02

This comment has been minimized.

Sign in to view

rustbot added S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. and removed S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. labels Sep 23, 2025

tgross35 approved these changes Sep 24, 2025

View reviewed changes

library/std/src/sys/fs/vexos.rs Outdated Show resolved Hide resolved

library/std/src/sys/fs/vexos.rs Outdated Show resolved Hide resolved

tropicaaal force-pushed the vex-std branch from 8ad25ac to d7717f8 Compare September 24, 2025 15:27

std: add support for armv7a-vex-v5 target

b2634e3

Co-authored-by: Lewis McClelland <lewis@lewismcclelland.me>

tropicaaal force-pushed the vex-std branch from d7717f8 to b2634e3 Compare September 24, 2025 17:12

bors added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Sep 24, 2025

Zalathar mentioned this pull request Sep 25, 2025

Rollup of 14 pull requests #147019

Merged

matthiaskrgr mentioned this pull request Sep 25, 2025

Rollup of 8 pull requests #147020

Closed

bors merged commit 0a34928 into rust-lang:master Sep 25, 2025
10 checks passed

rustbot added this to the 1.92.0 milestone Sep 25, 2025

tropicaaal mentioned this pull request Sep 25, 2025

std: fix warning in VEXos stdio module #147049

Merged

Add std support for armv7a-vex-v5 #145973

Add std support for armv7a-vex-v5 #145973

Uh oh!

Conversation

tropicaaal commented Aug 28, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Background

SDK Linkage

Future Work

Uh oh!

rustbot commented Aug 28, 2025

Uh oh!

rustbot commented Aug 28, 2025

Uh oh!

Uh oh!

Uh oh!

Uh oh!

tgross35 commented Aug 28, 2025

Uh oh!

This comment has been minimized.

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

tgross35 commented Aug 30, 2025

Uh oh!

rustbot commented Aug 30, 2025

Uh oh!

tropicaaal commented Aug 30, 2025

Uh oh!

tgross35 commented Aug 30, 2025

Uh oh!

bors commented Sep 3, 2025

Uh oh!

This comment has been minimized.

rustbot commented Sep 5, 2025

Uh oh!

This comment has been minimized.

tropicaaal commented Sep 23, 2025

Uh oh!

tgross35 left a comment • edited by rustbot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

tropicaaal commented Sep 24, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

tgross35 commented Sep 24, 2025

Uh oh!

tropicaaal commented Sep 24, 2025

Uh oh!

tgross35 commented Sep 24, 2025

Uh oh!

bors commented Sep 24, 2025

Uh oh!

Uh oh!

Uh oh!

Add `std` support for `armv7a-vex-v5` #145973

Add `std` support for `armv7a-vex-v5` #145973

tropicaaal commented Aug 28, 2025 •

edited

Loading

tgross35 left a comment •

edited by rustbot

Loading

tropicaaal commented Sep 24, 2025 •

edited

Loading