about summary refs log tree commit diff
path: root/src/tools
AgeCommit message (Collapse)AuthorLines
2023-07-06Auto merge of #113291 - oli-obk:pretty_print_mir_const, r=RalfJungbors-3/+4
Specialize `try_destructure_mir_constant` for its sole user (pretty printing) We can't remove the query, as we need to invoke it from rustc_middle, but can only implement it in mir interpretation/const eval. r? `@RalfJung` for a first round. While we could move all the logic into pretty printing, that would end up duplicating a bit of code with const eval, which doesn't seem great either.
2023-07-05C "memcpy" shim: ensure the pointers are validRalf Jung-0/+108
Also add tests for some other shims that already behave correctly
2023-07-05Move `TyCtxt::mk_x` to `Ty::new_x` where applicableBoxy-31/+35
2023-07-05Patch clippyOli Scherer-3/+4
2023-07-05Rollup merge of #113321 - BoxyUwU:move_constkind_to_typeir, r=oli-obkMichael Goulet-2/+2
Move `ty::ConstKind` to `rustc_type_ir` Needed this in another PR for custom debug impls, and this will also be required to move the new solver into a separate crate that does not use `TyCtxt` so that r-a and friends can depend on the trait solver. Rebased on top of #113325, only the second and third commits needs reviewing
2023-07-05Revert "use c literals in library"León Orell Valerian Liehr-0/+1
This reverts commit f212ba6d6d60963c8101bb24fc3e53fca80c046f.
2023-07-05Deal with falloutBoxy-2/+2
2023-07-04fix typoklensy-1/+1
2023-07-04tidy: exclude sh files from rust-installer tests from tidy bins checkklensy-1/+25
2023-07-04fix bash long lines and replace TODO with FIXMEklensy-11/+18
2023-07-04replace tabs with 4 spaces in .shklensy-804/+804
2023-07-04rust-installer and rls no longer submodule, so fix tidy walk listklensy-2/+2
2023-07-04rust-installer and rls no longer submodule, so fix rustfmt.tomlklensy-67/+29
2023-07-04Auto merge of #2960 - oli-obk:run_filter, r=oli-obkbors-1/+2
Restore test filtering by substring. Previously it was only looking for tests whose path was a prefix of the given filter fixes #2958
2023-07-04Auto merge of #2963 - RalfJung:start, r=RalfJungbors-2/+6
better error on missing #[start]
2023-07-04Restore test filtering by substring.Oli Scherer-1/+2
Previously it was only looking for tests whose path was a prefix of the given filter
2023-07-04better error on missing #[start]Ralf Jung-2/+6
2023-07-04Update debuginfo test runner to provide more useful outputTrevor Gross-108/+131
This change makes debuginfo tests more user friendly. Changes: - Print all lines that fail to match the patterns instead of just the first - Provide better error messages that also say what did match - Strip leading whitespace from directives so they are not skipped if indented - Improve documentation and improve nesting on some related items As an example, given the following debuginfo test with intentional fails: ```rust // from tests/debuginfo/rc_arc.rs // cdb-command:dx rc,d // cdb-check:rc,d : 111 [Type: alloc::rc::Rc<i32>] // cdb-check: [Reference count] : 11 [Type: core::cell FAIL::Cell<usize>] // cdb-check: [Weak reference count] : 2 [Type: core::cell FAIL::Cell<usize>] // ... ``` The current output (tested in #113313) only shows the first mismatch: ``` 2023-07-04T08:10:00.1939267Z ---- [debuginfo-cdb] tests\debuginfo\rc_arc.rs stdout ---- 2023-07-04T08:10:00.1942182Z 2023-07-04T08:10:00.1957463Z error: line not found in debugger output: [Reference count] : 11 [Type: core::cell FAIL::Cell<usize>] 2023-07-04T08:10:00.1958272Z status: exit code: 0 ``` With this change, you are able to see all failures in that check group, as well as what parts were successful. The output is now: ``` 2023-07-04T09:45:57.2514224Z error: check directive(s) from `C:\a\rust\rust\tests\debuginfo\rc_arc.rs` not found in debugger output. errors: 2023-07-04T09:45:57.2514631Z (rc_arc.rs:31) ` [Reference count] : 11 [Type: core::cell FAIL::Cell<usize>]` 2023-07-04T09:45:57.2514908Z (rc_arc.rs:32) ` [Weak reference count] : 2 [Type: core::cell FAIL::Cell<usize>]` 2023-07-04T09:45:57.2515181Z (rc_arc.rs:41) ` [Reference count] : 21 [Type: core::sync::atomic FAIL::AtomicUsize]` 2023-07-04T09:45:57.2515452Z (rc_arc.rs:50) `dyn_rc,d [Type: alloc::rc::Rc<dyn$<core::fmt FAIL::Debug> >]` 2023-07-04T09:45:57.2515695Z the following subset of check directive(s) was found successfully:: 2023-07-04T09:45:57.2516080Z (rc_arc.rs:30) `rc,d : 111 [Type: alloc::rc::Rc<i32>]` 2023-07-04T09:45:57.2516312Z (rc_arc.rs:35) `weak_rc,d : 111 [Type: alloc::rc::Weak<i32>]` 2023-07-04T09:45:57.2516555Z (rc_arc.rs:36) ` [Reference count] : 11 [Type: core::cell::Cell<usize>]` 2023-07-04T09:45:57.2516881Z (rc_arc.rs:37) ` [Weak reference count] : 2 [Type: core::cell::Cell<usize>]` ... ``` Which makes it easier to see what did and didn't succeed without manual comparison against the source test file.
2023-07-04Auto merge of #113303 - compiler-errors:yeet-chalk, r=lcnrbors-11/+1
Remove chalk support from the compiler Removes chalk (`-Ztrait-solver=chalk`) from the compiler and prunes any dead code resulting from this, mainly: * Remove the chalk compatibility layer in `compiler/rustc_traits/src/chalk` * Remove the chalk flag `-Ztrait-solver=chalk` and its `TraitEngine` implementation * Remove `TypeWellFormedFromEnv` (and its many `bug!()` match arms) * Remove the chalk migration mode from compiletest * Remove the `chalkify` UI tests (do we want to keep any of these, but migrate them to `-Ztrait-solver=next`??) Fulfills rust-lang/types-team#93. r? `@jackh726`
2023-07-04Auto merge of #2957 - RalfJung:zulip, r=oli-obkbors-5/+11
send link to PR to Zulip
2023-07-03Remove compare modeMichael Goulet-8/+0
2023-07-03Remove chalk from the compilerMichael Goulet-3/+1
2023-07-03Upgrade to indexmap 2.0.0Josh Stone-1/+1
The new version was already added to the tree as an indirect dependency in #113046, but now our direct dependents are using it too.
2023-07-03vec tets: ensure pointer is still writeableRalf Jung-6/+6
2023-07-03remove outdated commentRalf Jung-1/+0
2023-07-03send link to PR to ZulipRalf Jung-4/+11
2023-07-03Silence clippy on FIXME'd code and fix the new lints otherwiseOli Scherer-2/+4
2023-07-03Update rustixNilstrieb-0/+2
The issue has been fixed.
2023-07-03link to PERMITTED_DEPENDENCIES in tidy errorNilstrieb-0/+9
2023-07-03fmtThe Miri Conjob Bot-35/+53
2023-07-03Merge from rustcThe Miri Conjob Bot-5921/+23330
2023-07-03Preparing for merge from rustcThe Miri Conjob Bot-1/+1
2023-07-02can't seem to avoid repeating the branch name...Ralf Jung-3/+3
2023-07-02more CI yml cleanupRalf Jung-7/+6
2023-07-02sadly 'gh' doesnt support all git upstream branch configsRalf Jung-2/+4
2023-07-02cargo updateNilstrieb-1/+3
Additional deps: equivalent: indexmap nu-ansi-term: tracing overload: nu-ansi-term
2023-07-02cronjob auto-PR: try to fix setting the remote branchRalf Jung-4/+2
2023-07-02Auto merge of #2950 - icewind1991:cargo-miri-rustc-error, r=RalfJungbors-1/+5
cargo-miri: better error message when RUSTC is not set Currently, when running `cargo-miri` instead of `cargo miri` you get a very confusing. ``` thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: NotPresent', src/tools/miri/cargo-miri/src/main.rs:83:41 ``` error. This replaces that with a message telling them to use `cargo miri`
2023-07-02cron auto-PR: need to set upstream branchRalf Jung-2/+2
2023-07-02cargo-miri: better error message when RUSTC is not setRobin Appelman-1/+5
2023-07-02Fix compile-test tests to work with the new ui_test cratePhilipp Krones-9/+3
2023-07-02Fix valtree changesPhilipp Krones-2/+2
2023-07-02Merge commit '37f4c1725d3fd7e9c3ffd8783246bc5589debc53' into clippyupPhilipp Krones-5828/+21798
2023-07-02CI cleanupRalf Jung-8/+3
2023-07-02cronjob auto-PR: fetch more of the historyRalf Jung-2/+2
2023-07-02cronjob auto-PR: make sure we are on a branchRalf Jung-2/+6
2023-07-02Auto merge of #112718 - oli-obk:SIMD-destructure_mir_const, r=cjgillotbors-14/+62
Make simd_shuffle_indices use valtrees This removes the second-to-last user of the `destructure_mir_constant` query. So in a follow-up we can remove the query and just move the query provider function directly into pretty printing (which is the last user). cc `@rust-lang/clippy` there's a small functional change, but I think it is correct?
2023-07-01fix compiletest crashJan-Mirko Otter-1/+1
2023-07-01Put `LayoutError` behind reference to shrink resultNilstrieb-1/+1
`LayoutError` is 24 bytes, which is bigger than the `Ok` types, so let's shrink that.
2023-07-01Auto merge of #113225 - calebcartwright:sync-rustfmt, r=calebcartwrightbors-49/+1081
Update Rustfmt (add let-else support) Adds let-else formatting support Bit more detail in: https://github.com/rust-lang/rustfmt/blob/master/CHANGELOG.md#160-2023-07-02 Accompanying blog post: https://github.com/rust-lang/blog.rust-lang.org/pull/1117 I know we're getting close to tool week, however, there's been extensive discussion and testing of the changes in this between both t-style and t-rustfmt. Our confidence level is extremely high, and even if it's only on nightly for a few days, I'd still much prefer that and being able to get this out with 1.72 vs having to push to 1.73 Closes https://github.com/rust-lang/rustfmt/issues/4914 cc `@rust-lang/style` for awareness
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-02-28 04:15:09 +0000