-
Notifications
You must be signed in to change notification settings - Fork 13.2k
Comparing changes
Open a pull request
base repository: rust-lang/rust
base: master
head repository: matthiaskrgr/rust
compare: rollup-eu8934o
- 10 commits
- 77 files changed
- 2 contributors
Commits on Mar 12, 2025
-
fix: wasm-bare targets compiling x86 builtins
Added sanity check to bootstrap to hard error on wasm builds without clang, and changed distribution image `dist-various-2` to use clang to build for official targets.
Configuration menu - View commit details
-
Copy full SHA for e1bb12d - Browse repository at this point
Copy the full SHA e1bb12dView commit details
Commits on Mar 13, 2025
-
Rollup merge of #126856 - onur-ozkan:remove-rls, r=clubby789
remove deprecated tool `rls` This tool has been deprecated for two years and now it only gives warning without doing anything useful. Zulip discussion: https://rust-lang.zulipchat.com/#narrow/stream/241545-t-release/topic/excluding.20rls.20from.20the.20release try-job: x86_64-gnu-distcheck
Configuration menu - View commit details
-
Copy full SHA for 3ad5bdd - Browse repository at this point
Copy the full SHA 3ad5bddView commit details -
Rollup merge of #133981 - aDotInTheVoid:document-docs-ids, r=fmease
rustdoc-json: Refractor and document Id's Closes #133780 While working on documenting Id's, I realized alot of the way they were generated was weird and unnecessary. Eg: 1. The fully uninterned id type was `(FullItemId, Option<FullItemId>)`, meaning it wasn't actually full! 2. None of the extra fields in `Option<FullItemId>` would ever be used 3. `imported_item_id` was a `rustdoc_json_types::Id` instead of a simpler `DefId`. I believe the new implementation still covers all the same cases, but in a more principled way (and explaining why each piece is needed). This was written to be reviewed commit-by-commit, but it might be easier to review all at once if you're not interested in tracking how the original code became the final code. cc `@its-the-shrimp` r? `@fmease`
Configuration menu - View commit details
-
Copy full SHA for 65c1eef - Browse repository at this point
Copy the full SHA 65c1eefView commit details -
Rollup merge of #136842 - randomPoison:trusty-libstd-v3, r=ChrisDenton
Add libstd support for Trusty targets This PR adds support for `alloc` and `std` for the Trusty targets based on the internal patches used in Android. The original patches can be seen [here](https://android.googlesource.com/toolchain/android_rust/+/refs/heads/main/patches/development/rustc-0023-Add-Trusty-OS-support-to-Rust-std.patch) and [here](https://android.googlesource.com/toolchain/android_rust/+/refs/heads/main/patches/development/rustc-0054-Add-std-os-fd-support-for-Trusty.patch). Please let me know if there's any additional context I need to add.
Configuration menu - View commit details
-
Copy full SHA for 2f467f0 - Browse repository at this point
Copy the full SHA 2f467f0View commit details -
Rollup merge of #137355 - thaliaarchi:io-optional-methods/sgx, r=Chri…
…sDenton Implement `read_buf` and vectored read/write for SGX stdio Implement `read_buf`, `read_vectored`, and `write_vectored` for the SGX stdio types. Additionally, extend `User<T>::copy_to_enclave` to work for copying to uninitialized values and fix unsoundness in `UserRef<[T]>::copy_to_enclave_vec`. cc `@jethrogb` Tracked in #136756
Configuration menu - View commit details
-
Copy full SHA for a490334 - Browse repository at this point
Copy the full SHA a490334View commit details -
Rollup merge of #137457 - JayAndJef:issue-132802-fix, r=Kobzol
fix for issue 132802: x86 code in `wasm32-unknown-unknown` binaries This is a direct fix for issue [132802](#132802). Followed the outline as follows: > * give a hard error in bootstrap when using gcc to compile for wasm > * change our CI to use clang instead of gcc > * add a test that compiling a sample program for wasm32-unknown doesn't give any linker warnings The `test-various` ci job was also changed. try-job: test-various try-job: dist-various-2 try-job: x86_64-msvc-1
Configuration menu - View commit details
-
Copy full SHA for 780b30a - Browse repository at this point
Copy the full SHA 780b30aView commit details -
Rollup merge of #138162 - ehuss:library-2024, r=cuviper
Update the standard library to Rust 2024 This updates the standard library to Rust 2024. This includes the following notable changes: - Macros are updated to use new expression fragment specifiers. This PR includes a test to illustrate the changes, primarily allowing `const {...}` expressions now. - Some tests show a change in MIR drop order. We do not believe this will be an observable change ([see zulip discussion](https://rust-lang.zulipchat.com/#narrow/channel/268952-edition/topic/standard.20library.20migration/near/500972873)). Fixes #133081
Configuration menu - View commit details
-
Copy full SHA for 609def6 - Browse repository at this point
Copy the full SHA 609def6View commit details -
Rollup merge of #138273 - petrochenkov:nonatroot, r=bjorn3
metadata: Ignore sysroot when doing the manual native lib search in rustc This is the opposite alternative to #138170 and another way to make native library search consistent between rustc and linker. This way the directory list searched by rustc is still a prefix of the directory list considered by linker, but it's a shorter prefix than in #138170. We can include the sysroot directories into rustc's search again later if the issues with #138170 are resolved, it will be a backward compatible change. This may break some code doing weird things on unstable rustc, or tier 2-3 targets, like bundling `libunwind.a` or sanitizers into something. Note that this doesn't affect shipped `libc.a`, because it lives in `self-contained` directories in sysroot, and `self-contained` sysroot is already not included into the rustc's search. All libunwind and sanitizer libs should be moved to `self-contained` sysroot too eventually. With the consistent search directory list between rustc and linker we can make rustc own the native library search (at least for static libs) and use linker search only as a fallback (like in #123436). This will allow addressing issues like #132394 once and for all on all targets. r? `@bjorn3`
Configuration menu - View commit details
-
Copy full SHA for 21fd604 - Browse repository at this point
Copy the full SHA 21fd604View commit details -
Rollup merge of #138346 - folkertdev:naked-asm-windows-endef, r=Chris…
…Denton naked functions: on windows emit `.endef` without the symbol name tracking issue: #90957 fixes #138320 The `.endef` directive does not take the name as an argument. Apparently the LLVM x86_64 parser does accept this, but on i686 it's rejected. In general `i686` does some special name mangling stuff, so it's good to include it in the naked function tests. r? ```@ChrisDenton``` (because windows)
Configuration menu - View commit details
-
Copy full SHA for 67fd34a - Browse repository at this point
Copy the full SHA 67fd34aView commit details -
Rollup merge of #138370 - cuviper:try_oom_error, r=jhpratt
Simulate OOM for the `try_oom_error` test We can create the expected error manually, rather than trying to produce a real one, so the error conversion test can run on all targets. Before, it was only running on 64-bit and not miri. In Fedora, we also found that s390x was not getting the expected error, "successfully" allocating the huge size because it was optimizing the real `malloc` call away. It's possible to counter that by looking at the pointer in any way, like a debug print, but it's more robust to just deal with errors directly, since this test is only about conversion. Related: #133806
Configuration menu - View commit details
-
Copy full SHA for 87d384f - Browse repository at this point
Copy the full SHA 87d384fView commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff master...rollup-eu8934o