about summary refs log tree commit diff
AgeCommit message (Collapse)AuthorLines
2023-07-15Remove unused `bootstrap::util::CiEnv` enumjyn-10/+0
the right one is `build_helper::CiEnv`; this one wasn't even used.
2023-07-15Auto merge of #113514 - jyn514:more-gha-groups, r=oli-obkbors-65/+184
Add even more GHA log groups This also adds a dynamic check that we don't emit nested groups, since GHA currently doesn't support them. r? `@oli-obk`
2023-07-14fix another nesting issuejyn-4/+4
2023-07-14fix another GHA log panicjyn-0/+3
2023-07-14add a couple more groupsjyn-7/+12
- group rustdoc-js-std - group rust-installer/test.sh
2023-07-14Add `track_caller` to builder.msgjyn-0/+9
this makes the panics on nested GHA groups more useful
2023-07-14put configure behind a groupjyn-1/+5
2023-07-14don't print download progress in CIjyn-3/+8
2023-07-14Add must_use to `msg_` functionsjyn-45/+67
This caught several places which weren't waiting until the command finished to drop the Group. I also took the liberty of calling `msg_sysroot_tool` from `run_cargo_test` to reduce code duplication and make errors like this less likely in the future.
2023-07-14Add GHA log groups for tool testsjyn-0/+20
2023-07-14Make sure toolstates.json ends in a newlinejyn-1/+4
This avoids the following broken logging in CI: ``` {"book":"test-pass","reference":"test-pass","rustbook":"test-fail","rust-by-example":"test-pass","nomicon":"test-pass","embedded-book":"test-pass","edition-guide":"test-pass"}::group::Building bootstrap ```
2023-07-14fix nested GHA groups (redux)jyn-10/+6
2023-07-14Don't checkout the LLVM submodule in `x dist --dry-run`jyn-1/+3
We don't actually need it and it's quite slow.
2023-07-14Don't nest GHA groups in `check::Std`jyn-0/+1
2023-07-14Add even more GHA log groupsjyn-18/+67
This also adds a dynamic check that we don't emit nested groups, since GHA currently doesn't support them.
2023-07-14Auto merge of #113471 - compiler-errors:new-solver-norm-escaping, r=lcnrbors-22/+55
Allow escaping bound vars during `normalize_erasing_regions` in new solver Add `AllowEscapingBoundVars` to `deeply_normalize`, and use it in the new solver in the `query_normalize` routine. Ideally, we'd make all `query_normalize` calls handle pass in `AllowEscapingBoundVars` individually, because really the only `query_normalize` call that needs `AllowEscapingBoundVars::Yes` is the one in `try_normalize_generic_arg_after_erasing_regions`, but I think that's kind of overkill. I am happy to be convinced otherwise, though. r? `@lcnr`
2023-07-14Auto merge of #113703 - matthiaskrgr:rollup-19uhwuh, r=matthiaskrgrbors-223/+416
Rollup of 9 pull requests Successful merges: - #113599 (Use maybe_body_owned_by for multiple suggestions) - #113662 (Rename VecDeque's `rotate_left` and `rotate_right` parameters) - #113681 (rustdoc-json: Add test for private supertrait.) - #113682 (trait system refactor ping: also apply to nested modules of `solve`) - #113685 (Print artifact sizes in `opt-dist`) - #113688 (llvm-wrapper: update for LLVM API change) - #113692 (tests: adapt for removal of -opaque-pointers in LLVM 17) - #113698 (Make it clearer that we're just checking for an RPITIT) - #113699 (update Miri) Failed merges: - #113625 (Structurally normalize in selection) r? `@ghost` `@rustbot` modify labels: rollup
2023-07-14Rollup merge of #113699 - RalfJung:miri, r=RalfJungMatthias Krüger-64/+33
update Miri This fixes a pretty nasty bug in the tag GC. r? ghost
2023-07-14Rollup merge of #113698 - compiler-errors:rpitit-check, r=spastorinoMatthias Krüger-10/+14
Make it clearer that we're just checking for an RPITIT Tiny nit to use `is_impl_trait_in_trait` more, to make it clearer that we're just checking whether a def-id is an RPITIT, rather than doing something meaningful with the `opt_rpitit_info`. r? `@spastorino`
2023-07-14Rollup merge of #113692 - krasimirgg:llvm-17-no-opaque, r=nikicMatthias Krüger-0/+2
tests: adapt for removal of -opaque-pointers in LLVM 17 The commit https://github.com/llvm/llvm-project/commit/53717cabf837a589dd54a47dd8b4b3b9677f0b85 removed the flag from LLVM. Found via our experimental rust + LLVM@HEAD bot: https://buildkite.com/llvm-project/rust-llvm-integrate-prototype/builds/20777#01895454-40b2-4e2f-978b-1294a83e1cce
2023-07-14Rollup merge of #113688 - krasimirgg:llvm-17-small-string, r=nikicMatthias Krüger-0/+1
llvm-wrapper: update for LLVM API change No functional changes intended. Adds an include for `llvm::SmallString`. Previously, this must have been implicitly provided by some of the existing headers. With recent LLVM changes, not anymore: https://buildkite.com/llvm-project/rust-llvm-integrate-prototype/builds/20776#01895448-44a4-4a1e-8407-9d41d0186132/209-690
2023-07-14Rollup merge of #113685 - Kobzol:opt-dist-binary-sizes, r=Mark-SimulacrumMatthias Krüger-5/+45
Print artifact sizes in `opt-dist` The Python PGO script printed a nice table of artifact sizes (`librustc_driver.so`, `libLLVM.so`, ...) at the end of the CI run, which was useful to quickly see the sizes of important files. I forgot to port this functionality into the Rust (`opt-dist`) version in https://github.com/rust-lang/rust/pull/112235. This PR fixes that. r? bootstrap
2023-07-14Rollup merge of #113682 - lcnr:toml-file, r=Mark-SimulacrumMatthias Krüger-1/+1
trait system refactor ping: also apply to nested modules of `solve`
2023-07-14Rollup merge of #113681 - aDotInTheVoid:rdj-priv-supertrait, r=GuillaumeGomezMatthias Krüger-0/+15
rustdoc-json: Add test for private supertrait. Helps with https://github.com/rust-lang/rust/issues/81359 r? ``@GuillaumeGomez``
2023-07-14Rollup merge of #113662 - pedroclobo:vec-deque-rotate, r=thomccMatthias Krüger-25/+25
Rename VecDeque's `rotate_left` and `rotate_right` parameters This pull request introduces a modification to the `VecDeque` collection, specifically the `rotate_left` and `rotate_right` functions, by renaming the parameter associated with these functions. The rationale behind this change is to provide clearer and more consistent naming for the parameter that specifies the number of places to rotate the double-ended queue. By using `n` as the parameter name in both functions, it becomes easier to understand and remember the purpose of the parameter.
2023-07-14Rollup merge of #113599 - chenyukang:yukang-fix-use-maybe_body_owned_by, ↵Matthias Krüger-118/+280
r=cjgillot Use maybe_body_owned_by for multiple suggestions This is a continued work from https://github.com/rust-lang/rust/pull/113567 We have several other suggestions not working for closure, this PR use `maybe_body_owned_by` to fix them and add test cases for them.
2023-07-14Auto merge of #109025 - cjgillot:refprop-dbg, r=JakobDegenbors-902/+704
Enable MIR reference propagation by default
2023-07-14Auto merge of #113591 - mdibaiee:genericargs-cleanup, r=oli-obkbors-4605/+4575
refactor(rustc_middle): Substs -> GenericArg resolves #110793 - [x] rename `SubstsRef` and `InternalSubsts` to `GenericArgsRef<'tcx>` and `GenericArgs<'tcx>`. - [x] rename variables and fields currently using `substs` to `args`. - [x] update the module name of `ty::subst` to `ty::generic_args` or sth. Make that module private and publicly reexport its content in the ty module. - [x] rename `EarlyBinder::subst(_identity)` to `EarlyBinder::instantiate(_identity)`. - [x] types called `[a-zA-Z]+Substs` renamed to `XArgs`. - [x] functions containing `substs` now use `args` or `generic_args` (mostly the former). However, the verb of "substituting" is still being used here and there, mostly in comments. I think that can be a separate PR as part of https://github.com/rust-lang/rust/issues/110254 to change the verb to `replace_generics` or something similar.
2023-07-14Make it clearer that we're just checking for an RPITITMichael Goulet-10/+14
2023-07-14assertion, commentMichael Goulet-0/+4
2023-07-14Allow escaping bound vars during normalize_erasing_regions in new solverMichael Goulet-22/+51
2023-07-14Print artifact sizes in `opt-dist`Jakub Beránek-5/+45
2023-07-14Auto merge of #2975 - RalfJung:flags, r=RalfJungbors-37/+10
remove compile-flags that are no longer needed We stopped running fail-tests with optimizations a while ago, so we don't need to explicitly set the opt-level to 0 any more.
2023-07-14remove compile-flags that are no longer neededRalf Jung-37/+10
2023-07-14tests: adapt for removal of -opaque-pointers in LLVM 17Krasimir Georgiev-0/+2
The commit https://github.com/llvm/llvm-project/commit/53717cabf837a589dd54a47dd8b4b3b9677f0b85 removed the flag from LLVM.
2023-07-14Bless codegen test.Camille GILLOT-1/+1
2023-07-14refactor(rustc_middle): Substs -> GenericArgMahdi Dibaiee-4605/+4575
2023-07-14llvm-wrapper: update for LLVM API changeKrasimir Georgiev-0/+1
No functional changes intended. Adds an include for llvm::SmallString. Previously, this must have been implicitly provided by some of the existing headers. With recent LLVM changes, not anymore: https://buildkite.com/llvm-project/rust-llvm-integrate-prototype/builds/20776#01895448-44a4-4a1e-8407-9d41d0186132/209-690
2023-07-14Auto merge of #112982 - lukas-code:bootstrap-alias-default-crates, ↵bors-89/+118
r=albertlarsan68 bootstrap: update defaults for `compiler` and `library` aliases * `x doc compiler` now documents all of compiler, not just `rustc_driver`. * `x doc` with compiler docs enabled now includes `rustc-main` and `rustc_smir`. `rustc_codegen_llvm` is only included if the LLVM backend is enabled, which is the default. * `x doc library` now excludes `sysroot`. * `x check compiler` and `x check library` now properly check tests/benches/examples of all compiler or library crates, respectively. Note that `x check compiler` will check the library artifacts, but not tests. fixes the fallout from https://github.com/rust-lang/rust/pull/111955, cc `@jyn514`
2023-07-14Auto merge of #2980 - RalfJung:span, r=RalfJungbors-13/+6
work around custom_mir span Cc https://github.com/rust-lang/rust/issues/113549
2023-07-14work around custom_mir spanRalf Jung-13/+6
2023-07-14Auto merge of #113328 - michaelwoerister:no_hashmap_in_typeck, r=cjgillot,lcnrbors-172/+212
Enable potential_query_instability lint in rustc_hir_typeck. Fix linting errors by using `FxIndex(Map|Set)` and `Unord(Map|Set)` as appropriate. Part of [MCP 533](https://github.com/rust-lang/compiler-team/issues/533). I really like the `potential_query_instability` lint! r? `@lcnr`
2023-07-14fix docs for `rustc_smir`Lukas Markeffsky-3/+4
2023-07-14bootstrap: update defaults for `compiler` and `library` aliasesLukas Markeffsky-86/+114
2023-07-14also apply to nested modules of `solve`lcnr-1/+1
2023-07-14Introduce ExtentUnord trait for collections that can safely consume UnordItems.Michael Woerister-26/+39
2023-07-14Enable potential_query_instability lint in rustc_hir_typeck.Michael Woerister-148/+175
Fix linting errors by using FxIndex(Map|Set) and Unord(Map|Set) as appropriate.
2023-07-14Auto merge of #113639 - ericmarkmartin:more-smir-types, r=oli-obkbors-3/+8
Add more ty conversions to smir add str, slice, and array to smir types r? `@spastorino`
2023-07-14rustdoc-json: Add test for private supertrait.Alona Enraght-Moony-0/+15
2023-07-14Auto merge of #113609 - nnethercote:maybe_lint_level_root_bounded-cache, ↵bors-32/+71
r=cjgillot Add a cache for `maybe_lint_level_root_bounded` `maybe_lint_level_root_bounded` is called many times and traces node sub-paths many times. This PR adds a cache that lets many of these tracings be skipped, avoiding lots of calls to functions like `Map::attrs` and `Map::parent_id`. r? `@cjgillot`
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-05-06 19:37:09 +0000