Rustc pull update

rust-version

@@ -1 +1 @@
-f2b291d902bfde7d7f209fc3a64908134bcef201
+a31c27a887b40df16ab9dfb8c9f7924636092509

src/tests/directives.md

@@ -78,7 +78,7 @@ See [Controlling pass/fail expectations](ui.md#controlling-passfail-expectations
 | `run-fail`                  | Program must exit with code `1..=127`       | `ui`                                      | N/A             |
 | `run-crash`                 | Program must crash                          | `ui`                                      | N/A             |
 | `run-fail-or-crash`         | Program must `run-fail` or `run-crash`      | `ui`                                      | N/A             |
-| `ignore-pass`               | Ignore `--pass` flag                        | `ui`                                      | N/A             |
+| `no-pass-override`          | Ignore `--pass` flag                        | `ui`                                      | N/A             |
 | `dont-check-failure-status` | Don't check exact failure status (i.e. `1`) | `ui`, `incremental`                       | N/A             |
 | `failure-status`            | On failure, the compiler must exit with this status code. To expect an ICE, use `//@ failure-status: 101`. | `ui`, `incremental` | Any `u16` |
 | `should-fail`               | Compiletest self-test                       | All                                       | N/A             |
@@ -133,7 +133,7 @@ means the test won't be compiled or run.
 Some examples of `X` in `ignore-X` or `only-X`:
 
 - A full target triple: `aarch64-apple-ios`
-- Architecture: `aarch64`, `arm`, `mips`, `wasm32`, `x86_64`, `x86`,
+- Architecture: `aarch64`, `arm`, `csky`, `mips`, `mips64`, `wasm32`, `x86_64`, `x86`,
   ...
 - OS: `android`, `emscripten`, `freebsd`, `ios`, `linux`, `macos`, `windows`,
   ...

src/tests/running.md

@@ -202,7 +202,7 @@ There are a few options for running tests:
 
 Pass UI tests now have three modes, `check-pass`, `build-pass` and `run-pass`.
 When `--pass $mode` is passed, these tests will be forced to run under the given
-`$mode` unless the directive `//@ ignore-pass` exists in the test file.
+`$mode` unless the directive `//@ no-pass-override` exists in the test file.
 For example, you can run all the tests in `tests/ui` as `check-pass`:
 
 ```text

src/tests/ui.md

@@ -492,7 +492,7 @@ Using `--pass check` can run the UI
 test suite much faster (roughly twice as fast on my system), though obviously
 not exercising as much.
 
-The `ignore-pass` directive can be used to ignore the `--pass` CLI flag if the
+The `no-pass-override` directive can be used to ignore the `--pass` CLI flag if the
 test won't work properly with that override.