-
Notifications
You must be signed in to change notification settings - Fork 13.8k
Rollup of 4 pull requests #147657
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rollup of 4 pull requests #147657
Conversation
we should not get the certainty from the current result of the provisional cache entry
…tion for reusing it
Co-authored-by: Josh Triplett <josh@joshtriplett.org>
Co-authored-by: Josh Triplett <josh@joshtriplett.org>
Co-authored-by: Josh Triplett <josh@joshtriplett.org>
Co-authored-by: Josh Triplett <josh@joshtriplett.org>
fix 2 search graph bugs wooooooooops, i should really run the fuzzer even when not changing the structure of the search graph as a whole :3 fixes the `ml-kem` ICE in the next-solver crater run r? `@BoxyUwU`
…=joshtriplett Implement fs api set_times and set_times_nofollow implementation of rust-lang#147455 r? `@joshtriplett`
…etrochenkov `proc_macro` cleanups (3/N) Followup to rust-lang#147386, which removed the old `Decode` trait. Can be reviewed commit by commit.
std: implement `pal::os::exit` for VEXos This PR provides a more "proper" implementation of process exiting in VEXos programs by going through `vexSystemExitRequest` rather than calling `intrinsics::abort`, which exits using an undefined instruction trap. This matches the existing implementation of `rt::abort_internal` and therefore makes `std::process::exit` have the same behavior as returning from main on VEXos targets.
@bors r+ rollup=never p=5 |
There are 2 more rollup=never PRs waiting in the queue, and also there are currently about 8 PRs that could be rolled up (including rollup=iffy ones, which tend to get starved if people leave them out of rollups). So it might be a good idea to close this small rollup, and either make a rollup of everything, or let the rollup=never PRs run for a bit and then do a larger rollup later. What do you think? |
Sure. |
Successful merges:
proc_macro
cleanups (3/N) #147497 (proc_macro
cleanups (3/N))pal::os::exit
for VEXos #147594 (std: implementpal::os::exit
for VEXos)r? @ghost
@rustbot modify labels: rollup
Create a similar rollup