about summary refs log tree commit diff
path: root/src
AgeCommit message (Collapse)AuthorLines
2025-06-10ci: split x86_64-gnu-tools jobMarcoIeni-56/+125
2025-06-10Avoid cloning `self.index` in `after_krate`.Nicholas Nethercote-2/+4
It can be very big. This reduces peak memory usage for some `--output-format=json` runs by up to 8%.
2025-06-10float tests: test non-determinism for more operationsRalf Jung-22/+25
2025-06-10Merge pull request #4394 from RalfJung/smallvecRalf Jung-0/+99
add SmallVec test
2025-06-10add SmallVec testRalf Jung-0/+99
2025-06-10Simplify `JsonRenderer`.Nicholas Nethercote-10/+9
- It doesn't need to be cloneable. - Some of the `Rc`s and `RefCell`s aren't doing anything. - `after_krate` can consume `self`.
2025-06-10sync max_fundamental_align with alloc crateRalf Jung-4/+7
2025-06-10Auto merge of #142109 - weihanglo:update-cargo, r=weihanglobors-0/+0
Update cargo 18 commits in 64a12460708cf146e16cc61f28aba5dc2463bbb4..fc1518ef02b77327d70d4026b95ea719dd9b8c51 2025-05-30 18:25:08 +0000 to 2025-06-06 04:49:44 +0000 - fix: Make UI tests handle hyperlinks consistently (rust-lang/cargo#15640) - Update "time out" to "timeout" (rust-lang/cargo#15637) - fix(workspace): reload current manifest path member only (rust-lang/cargo#15633) - Update dependencies (rust-lang/cargo#15635) - fix(publish): Don't tell people to ctrl-c without knowing consequences (rust-lang/cargo#15632) - refactor: clean up `clippy::perf` lint warnings (rust-lang/cargo#15631) - fix(package): Skip registry check if its not needed (rust-lang/cargo#15629) - Add --offline for comp (rust-lang/cargo#15623) - cargo-credential-libsecret: load libsecret only once (rust-lang/cargo#15295) - test(publish): Improvements in prep for `-Zpackage-workspace` stabilization (rust-lang/cargo#15628) - fix(package): Allow packaging of self-cycles with -Zpackage-workspace (rust-lang/cargo#15626) - docs: clarify `--all-features` not available for all commmands (rust-lang/cargo#15572) - Remove double reference in Shell::print_json (rust-lang/cargo#15460) - fix(trim-paths): remap all paths to `build.build-dir` (rust-lang/cargo#15614) - test(trim-paths): enable more tests for windows-msvc (rust-lang/cargo#15621) - fix(fingerprint): explicit reason rather than "stale; unknown reason" (rust-lang/cargo#15617) - Fix cargo add overwriting symlinked Cargo.toml files (rust-lang/cargo#15281) - chore(deps): update alpine docker tag to v3.22 (rust-lang/cargo#15616) r? ghost
2025-06-10fmtThe Miri Cronjob Bot-1/+0
2025-06-10Merge from rustcThe Miri Cronjob Bot-384/+772
2025-06-10Preparing for merge from rustcThe Miri Cronjob Bot-1/+1
2025-06-10Auto merge of #142250 - lnicola:sync-from-ra, r=lnicolabors-1085/+2373
Subtree update of `rust-analyzer` r? `@ghost`
2025-06-10rustdoc: Refractor `clean_ty_generics`Alona Enraght-Moony-74/+19
2025-06-09Don't create .msi installer for gnullvm hostsMateusz Mikuła-1/+2
WIX toolset works only on Windows hosts and we need to boostrap this host.
2025-06-09Auto merge of #138062 - LorrensP-2158466:miri-enable-float-nondet, r=RalfJungbors-62/+329
Enable Non-determinism of float operations in Miri and change std tests Links to [#4208](https://github.com/rust-lang/miri/issues/4208) and [#3555](https://github.com/rust-lang/miri/issues/3555) in Miri. Non-determinism of floating point operations was disabled in rust-lang/rust#137594 because it breaks the tests and doc-tests in core/coretests and std. This PR enables some of them. This pr includes the following changes: - Enables the float non-determinism but with a lower relative error of 4ULP instead of 16ULP - These operations now have a fixed output based on the C23 standard, except the pow operations, this is tracked in [#4286](https://github.com/rust-lang/miri/issues/4286#issue-3010677983) - Changes tests that made incorrect assumptions about the operations, not to make that assumption anymore (from `assert_eq!` to `assert_approx_eq!`. - Changed the doctests of the stdlib of these operations to compare against fixed constants instead of `f*::EPSILON`, which now succeed with Miri and `-Zmiri-many-seeds` - Added a constant `APPROX_DELTA` in `std/tests/floats/f32.rs` which is used for approximation tests, but with a different value when run in Miri. This is to make these tests succeed. - Added tests in the float tests of Miri to test the C23 behaviour. Fixes https://github.com/rust-lang/miri/issues/4208
2025-06-09native-lib: update readme (to mention folders in header)Ralf Jung-10/+12
2025-06-09native_lib: skip to next .so if function was in dependency of the firstRalf Jung-12/+13
2025-06-10platform-support.md: Mention specific Linux kernel version or laterTeoh Han Hui-19/+19
2025-06-09Auto merge of #142253 - tgross35:rollup-img49op, r=tgross35bors-3/+42
Rollup of 5 pull requests Successful merges: - rust-lang/rust#140767 (Stabilize `sha512`, `sm3` and `sm4` for x86) - rust-lang/rust#141001 (Make NonZero<char> possible) - rust-lang/rust#141993 (Use the in-tree `compiler-builtins` for the sysroot) - rust-lang/rust#142208 (Always consider `const _` items as live for dead code analysis) - rust-lang/rust#142238 (stabilize nonnull_provenance) r? `@ghost` `@rustbot` modify labels: rollup
2025-06-09Merge pull request #19930 from regexident/dyn-semantics-take-twoDavid Barsky-2/+18
Make `Semantics<'db, DB>` support `Semantics<'db, dyn HirDatabase>`, take two
2025-06-09Rollup merge of #141993 - tgross35:use-in-tree-builtins, r=bjorn3Trevor Gross-3/+42
Use the in-tree `compiler-builtins` for the sysroot Many of `std`'s dependency have a dependency on the crates.io `compiler-builtins` when used with the feature `rustc-std-workspace-core`. Use a Cargo patch to select the in-tree version instead. `compiler-builtins` is also added as a dependency of `rustc-std-workspace-core` so these crates can remove their crates.io dependency in the future. Zulip discussion: [#t-compiler > Using in-tree compiler-builtins](https://rust-lang.zulipchat.com/#narrow/channel/131828-t-compiler/topic/Using.20in-tree.20compiler-builtins/with/522445336) Once this merges, the following PRs will need to make it to a release for the relevant crates: - https://github.com/rust-lang/getopts/pull/119 (can merge at any time) - https://github.com/rust-lang/hashbrown/pull/625 (can merge at any time) - https://github.com/rust-lang/stdarch/pull/1825 - https://github.com/rust-lang/rustc-demangle/pull/80 - https://github.com/rust-lang/cfg-if/pull/84 - https://github.com/unicode-rs/unicode-width/pull/77 The above should cover all tier 1 targets with no `std` features enabled. The remaining cover the rest: - https://github.com/alexcrichton/dlmalloc-rs/pull/50 (wasm, xous, sgx) - https://github.com/gimli-rs/gimli/pull/769 - https://github.com/r-efi/r-efi/pull/89 (efi) - https://github.com/r-efi/r-efi-alloc/pull/9 (efi) - https://github.com/fortanix/rust-sgx/pull/770 (sgx) - https://github.com/hermit-os/hermit-rs/pull/718 (hermit) - https://github.com/bytecodealliance/wasi-rs/pull/108 (wasi) - https://github.com/gimli-rs/addr2line/pull/345 - https://github.com/oyvindln/adler2/pull/2 - https://github.com/BurntSushi/memchr/pull/180 - https://github.com/Frommi/miniz_oxide/pull/173 - https://github.com/gimli-rs/object/pull/777 try-job: x86_64-gnu try-job: test-various
2025-06-09Merge pull request #4376 from yoctocell/tb-interior-mut-flagRalf Jung-35/+154
TB: Add flag to disable the more precise interior mutability tracking
2025-06-09Initialize the execution context in parse_inner, start using dry run from ↵bit-aloo-28/+29
the execution context, add getters and setters in the config, and update the tests and other relevant areas accordingly.
2025-06-09Add `-Zmiri-tree-borrows-no-precise-interior-mut` flagXinglu Chen-35/+154
2025-06-09Auto merge of #142241 - Kobzol:disable-ci-rustc-on-ci, r=jieyouxubors-3/+5
Disable download-rustc on CI Should resolve https://rust-lang.zulipchat.com/#narrow/channel/326414-t-infra.2Fbootstrap/topic/aarch64-apple.20try.20job.20doesn.27t.20work/with/522659759. r? `@jieyouxu`
2025-06-09remove execution context from flag module and correct the command invocation ↵bit-aloo-25/+19
according to suggestions
2025-06-09update dry_run value in exec_ctx and start forwarding exec_ctx verbose ↵bit-aloo-13/+5
methods via config
2025-06-09move all commands to new execution contextbit-aloo-174/+20
2025-06-09move all config command invocation to new execution context invocationbit-aloo-23/+32
2025-06-09moved git command to new exec contextbit-aloo-8/+3
2025-06-09move all download.rs method to new execution context command invocationbit-aloo-34/+13
2025-06-09covert uname to new extext methodbit-aloo-14/+8
2025-06-09moved curl to use new execution_contextbit-aloo-8/+10
2025-06-09moved sanity command to exec contextbit-aloo-2/+5
2025-06-09-Zretpoline and -Zretpoline-external-thunk flags (target modifiers) to ↵Andrew Zhogin-2/+3
enable retpoline-related target features
2025-06-09Merge from rust-lang/rustLaurențiu Nicola-11455/+17581
2025-06-09Preparing for merge from rust-lang/rustLaurențiu Nicola-1/+1
2025-06-09Auto merge of #142242 - matthiaskrgr:rollup-1sgx0ji, r=matthiaskrgrbors-302/+289
Rollup of 7 pull requests Successful merges: - rust-lang/rust#129121 (Stabilize `tcp_quickack`) - rust-lang/rust#142192 (De-duplicate f16 & f128 doctest attributes) - rust-lang/rust#142193 (add tests for pattern binding drop order edge cases) - rust-lang/rust#142222 (Dont make `ObligationCtxt`s with diagnostics unnecessarily) - rust-lang/rust#142228 (rustc-dev-guide subtree update) - rust-lang/rust#142231 (Run `calculate_matrix` job on `master` to cache citool builds) - rust-lang/rust#142232 (add `Cargo.lock` to CI-rustc allowed list for non-CI env) r? `@ghost` `@rustbot` modify labels: rollup
2025-06-09Rollup merge of #142232 - onur-ozkan:141986, r=KobzolMatthias Krüger-21/+34
add `Cargo.lock` to CI-rustc allowed list for non-CI env Changes to dependencies usually require modifying `Cargo.toml`, which would already invalidate the CI-rustc cache if done in non-allowed paths. On non-CI environment, it should be safe to add `Cargo.lock` to the list of allowed paths as there is no real risk aside from a very rare false positive in cases like minor bumps to non-allowed path dependencies without modifying the `Cargo.toml` files. Fixes rust-lang/rust#141986
2025-06-09Rollup merge of #142231 - Kobzol:master-cache-ci, r=marcoieniMatthias Krüger-6/+25
Run `calculate_matrix` job on `master` to cache citool builds As discussed in https://rust-lang.zulipchat.com/#narrow/channel/242791-t-infra/topic/PR.20ci.20seems.20much.20to.20slow/with/523028903, the current `rust-cache` solution for `citool` doesn't work, because we don't ever write to the cache from `master`, so the cache is empty on PR CI jobs. This PR runs the `calculate_matrix` job on `master`, with the only motivation to actually prime the cache. r? `@marcoieni`
2025-06-09Rollup merge of #142228 - tshepang:rust-push, r=jieyouxuMatthias Krüger-275/+230
rustc-dev-guide subtree update r? `@ghost`
2025-06-09Disable download-rustc on CIJakub Beránek-3/+5
2025-06-09add `Cargo.lock` to CI-rustc allowed list for non-CI envonur-ozkan-21/+34
Signed-off-by: onur-ozkan <work@onurozkan.dev>
2025-06-09Rollup merge of #142218 - ojeda:rfl, r=KobzolMatthias Krüger-2/+1
CI: rfl: move job forward to Linux v6.16-rc1 Another hopefully routine upgrade to Linux v6.16-rc1, just released. r? `@lqd` `@Kobzol` try-job: x86_64-rust-for-linux `@rustbot` label A-rust-for-linux `@bors` try
2025-06-09Rollup merge of #142211 - Kobzol:try-fast-submodule-checkout, r=Mark-SimulacrumMatthias Krüger-0/+8
Do not checkout GCC submodule for the tidy job This is not a fully general solution, but the GCC submodule checkout is so slow that I think it's worth it to special-case it. This brings down the time required to checkout submodules from ~1.5 minute to ~0.5 minute.
2025-06-09Rollup merge of #142160 - Urgau:check-cfg-bootstrap-only-rustc, r=KobzolMatthias Krüger-8/+13
Only allow `bootstrap` cfg in rustc & related Fixes https://github.com/rust-lang/rust/issues/142150 r? bootstrap
2025-06-09Rollup merge of #141751 - jieyouxu:remap, r=KobzolMatthias Krüger-10/+70
Remap compiler vs non-compiler sources differently (bootstrap side) See [#t-compiler/help > Span pointing to wrong file location (&#96;rustc-dev&#96; component)](https://rust-lang.zulipchat.com/#narrow/channel/182449-t-compiler.2Fhelp/topic/Span.20pointing.20to.20wrong.20file.20location.20.28.60rustc-dev.60.20component.29/with/521087083). The path remapping and unremapping for compiler sources (distributed via `rustc-dev` dist component) is broken because bootstrap currently remaps all sources unconditionally (if remapping is enabled) to the `/rustc/{hash}` form. However, the `rustc-dev` dist component (compiler sources) and `rust-src` dist component (library sources) unpacks differently: - `rust-src` unpacks sources to a path like `$sysroot/lib/rustlib/src/rust`, whereas - `rustc-dev` unpacks sources to a path like `$sysroot/lib/rustlib/rustc-src/rust`[^note], meaning that the compiler need to unremap them differently. But the same remapping means that the compiler has no way to distinguish between compiler and non-compiler (esp. standard library) sources. To remedy this, this PR adopts the approach of: - remapping compiler sources (corresponding to `rustc-dev` dist component) with `/rustc-dev/{hash}` (this is `RemapScheme::Compiler`), and - remapping non-compiler sources (corresponding to `rust-src` dist component or other non-compiler sources) with `/rustc/{hash}` (this is `RemapScheme::NonCompiler`). A different remapping allows the compiler to reverse the remapping differently. This PR implements the bootstrap side. A follow-up compiler-side change is needed to implement the unremapping change to address the reported issue completely. This PR introduces another env var `CFG_VIRTUAL_RUSTC_DEV_SOURCE_BASE_DIR` that is made available to the compiler when building compiler sources to know what the remap scheme for `rustc-dev` (`RemapScheme::Compiler`) is. Compiler sources are built with the compiler remapping scheme. As far as I know, this change should not introduce new regressions, because the compiler source unremapping (through `rustc-dev`) is already broken. [^note]: (Notice the `src` vs `rustc-src` difference.)
2025-06-09Do not checkout GCC submodule for the tidy jobJakub Beránek-0/+8
2025-06-09Run `calculate_matrix` job on the `master` branchJakub Beránek-1/+15
This allows us to reuse its cache on PR CI jobs.
2025-06-09Do not inherit environment variables in citool testsJakub Beránek-5/+10
So that we can make sure that they are reproducible locally.
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-07-13 12:35:55 +0000