rust/src/tools/compiletest, branch 1.82.0https://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=1.82.02024-08-30T07:14:31+00:00add borrows to NLL MIR dumps2024-08-30T07:14:31+00:00Rémy Rakicremy.rakic+github@gmail.com2024-08-28T21:17:44+00:00urn:sha1:dff3d3588d8ba35e4b730384d885c95e31e07953
explicitly disable `-Zmir-include-spans` in mir-opt tests
This will override the NLL default of true, and keep the blessed dumps
easier to work with.
strip whitespace for ignored tests reason comments2024-08-25T22:17:51+00:00Rémy Rakicremy.rakic+github@gmail.com2024-08-11T15:02:13+00:00urn:sha1:7963beda2481deb5bd01286b61386d599536a3b5compiletest: implement `needs-lvm-zstd` directive2024-08-25T22:17:51+00:00Rémy Rakicremy.rakic+github@gmail.com2024-08-10T15:02:13+00:00urn:sha1:5b374631df79f879560f3a4d041290e152c05ab0Revert "compiletest: use `std::fs::remove_dir_all` now that it is available"2024-08-22T15:55:06+00:00许杰友 Jieyou Xu (Joe)jieyouxu@outlook.com2024-08-22T15:55:06+00:00urn:sha1:3957f3933904075a348eda68ae3d34f9f4914116
This reverts commit 75ed08972703798888fceff12b3217408ca6a4b5.
compiletest: use `std::fs::remove_dir_all` now that it is available2024-08-20T09:25:05+00:00许杰友 Jieyou Xu (Joe)39484203+jieyouxu@users.noreply.github.com2024-08-20T09:24:56+00:00urn:sha1:75ed08972703798888fceff12b3217408ca6a4b5Auto merge of #129218 - saethlin:gdb-supports-rust-now, r=jieyouxu2024-08-19T12:16:20+00:00borsbors@rust-lang.org2024-08-19T12:16:20+00:00urn:sha1:4fe1e2bd5bf5a6f1cb245f161a5e9d315766f103
Delete debuginfo test suite infra for gdb without Rust support and lldb with Rust support
Implements https://github.com/rust-lang/rust/issues/128953
I also deleted all the `min-lldb-version: 310` comments, because the oldest compatible distro I can find is Ubuntu 16.04 which ships lldb 3.8, though of course the package that the Ubuntu maintainers put together for that is broken.
Rocky Linux 8 amusingly ships lldb 17, even though it has a similar glibc and kernel version.
This PR is multiple highly mechanical changes. Some of the commits were created by just running `sed`. You may find it easier to review each commit separately.
Auto merge of #125854 - beetrees:zst-arg-abi, r=estebank2024-08-18T22:15:41+00:00borsbors@rust-lang.org2024-08-18T22:15:41+00:00urn:sha1:d0293c6cf22cb37f04ac90a52d1fc259362acc5b
Move ZST ABI handling to `rustc_target`
Currently, target specific handling of ZST function call ABI (specifically passing them indirectly instead of ignoring them) is handled in `rustc_ty_utils`, whereas all other target specific function call ABI handling is located in `rustc_target`. This PR moves the ZST handling to `rustc_target` so that all the target-specific function call ABI handling is in one place. In the process of doing so, this PR fixes #125850 by ensuring that ZST arguments are always correctly ignored in the x86-64 `"sysv64"` ABI; any code which would be affected by this fix would have ICEd before this PR. Tests are also added using `#[rustc_abi(debug)]` to ensure this behaviour does not regress.
Fixes #125850
Clean up compiletest2024-08-18T20:58:26+00:00Ben Kimockkimockb@gmail.com2024-08-17T22:09:27+00:00urn:sha1:e2523c18427db0a6b28b7dc8c12a5a65011bef49Delete compiletest support for gdbg2024-08-18T16:39:07+00:00Ben Kimockkimockb@gmail.com2024-08-17T21:37:09+00:00urn:sha1:e1a82c96341747e486c72139748d3bc3d538f669Rollup merge of #129049 - Zalathar:json-like, r=jieyouxu2024-08-13T19:11:14+00:00Matthias Krügermatthias.krueger@famsik.de2024-08-13T19:11:14+00:00urn:sha1:65054ed35edeb6293c247020ae2259e8d1f0d984
compiletest: Don't panic on unknown JSON-like output lines
The `json::extract_rendered` function is called for both compiler output and non-compiler output, so it's inappropriate to panic just because a line starting with `{` didn't contain a compiler output message.
It is called from two places: when checking the output of a `ui` test process, and when printing the output of an arbitrary non-passing `ProcRes`. So unfortunately there's currently no easy way to know for sure whether it is seeing compiler output or not. Fortunately, neither call site appears to be relying on this panic; it's just an overzealous internal check.
Fixes #126373.