rust/tests/ui/sanitizer, branch perf-tmphttps://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=perf-tmp2025-09-26T13:33:48+00:00Ignore more failing ui tests for GCC backend2025-09-26T13:33:48+00:00Guillaume Gomezguillaume1.gomez@gmail.com2025-09-26T11:59:06+00:00urn:sha1:a535c7be5444fb6584eecc99f53e6cdb710ff70f-Zsanitize and -Zsanitizer-cfi-normalize-integers flags are now target modifiers with custom consistency check function2025-08-21T09:08:00+00:00Andrew Zhoginandrew.zhogin@gmail.com2025-03-20T05:43:44+00:00urn:sha1:6d637dfeccd7d22523e584203e666535db878165Remove the no_sanitize attribute in favor of sanitize2025-08-18T08:45:28+00:00Bastian Kerstingbkersting@google.com2025-06-18T13:47:44+00:00urn:sha1:95bdb34494ad795f552cab7a0eb7bfd2e98ef033
This removes the #[no_sanitize] attribute, which was behind an unstable
feature named no_sanitize. Instead, we introduce the sanitize attribute
which is more powerful and allows to be extended in the future (instead
of just focusing on turning sanitizers off).
This also makes sanitize(kernel_address = ..) attribute work with
-Zsanitize=address
To do it the same as how clang disables address sanitizer, we now
disable ASAN on sanitize(kernel_address = "off") and KASAN on
sanitize(address = "off").
The same was added to clang in https://reviews.llvm.org/D44981.
Implement the #[sanitize(..)] attribute2025-08-18T08:30:00+00:00Bastian Kerstingbkersting@google.com2025-06-18T12:53:34+00:00urn:sha1:3ef065bf872ce62a18336dca0daf47b3e9f7da64
This change implements the #[sanitize(..)] attribute, which opts to
replace the currently unstable #[no_sanitize]. Essentially the new
attribute works similar as #[no_sanitize], just with more flexible
options regarding where it is applied. E.g. it is possible to turn
a certain sanitizer either on or off:
`#[sanitize(address = "on|off")]`
This attribute now also applies to more places, e.g. it is possible
to turn off a sanitizer for an entire module or impl block:
```rust
\#[sanitize(address = "off")]
mod foo {
fn unsanitized(..) {}
#[sanitize(address = "on")]
fn sanitized(..) {}
}
\#[sanitize(thread = "off")]
impl MyTrait for () {
...
}
```
This attribute is enabled behind the unstable `sanitize` feature.
Add `ignore-backends` annotations in failing GCC backend ui tests2025-07-23T11:48:04+00:00Guillaume Gomezguillaume1.gomez@gmail.com2025-07-23T11:31:22+00:00urn:sha1:de93fb13feeb6263bef61d4035e78ab8651c5714tests: Require `run-fail` ui tests to have an exit code (`SIGABRT` not ok)2025-07-19T16:44:07+00:00Martin Nordholtsmartin.nordholts@codetale.se2025-06-25T05:56:40+00:00urn:sha1:e1d4f2a0c297690ddfc24815de57539f532f2471
And introduce two new directives for ui tests:
* `run-crash`
* `run-fail-or-crash`
Normally a `run-fail` ui test like tests that panic shall not be
terminated by a signal like `SIGABRT`. So begin having that as a hard
requirement.
Some of our current tests do terminate by a signal/crash however.
Introduce and use `run-crash` for those tests. Note that Windows crashes
are not handled by signals but by certain high bits set on the process
exit code. Example exit code for crash on Windows: `0xc000001d`.
Because of this, we define "crash" on all platforms as "not exit with
success and not exit with a regular failure code in the range 1..=127".
Some tests behave differently on different targets:
* Targets without unwind support will abort (crash) instead of exit with
failure code 101 after panicking. As a special case, allow crashes for
`run-fail` tests for such targets.
* Different sanitizer implementations handle detected memory problems
differently. Some abort (crash) the process while others exit with
failure code 1. Introduce and use `run-fail-or-crash` for such tests.
Workaround a MemorySanitizer test issue2025-07-04T21:47:28+00:00Scott McMurrayscottmcm@users.noreply.github.com2025-07-04T21:47:28+00:00urn:sha1:d020e38fa229d184026ac9b1a7ea73b9f99e8e7aDetect more cases of unused_parens around types2025-07-01T06:56:20+00:00Benjamin Schulzbenjamin.schulz@sap.com2025-06-04T17:03:18+00:00urn:sha1:7d6764a45bd05913e7f34a8fbba12bf384b0269acompiletest: Improve diagnostics for line annotation mismatches2025-06-23T18:30:56+00:00Vadim Petrochenkovvadim.petrochenkov@gmail.com2025-05-03T12:53:52+00:00urn:sha1:7a4f09c2240ef2eb4d1e383f0d471b85ce8d0720Change __rust_no_alloc_shim_is_unstable to be a function2025-06-16T17:54:07+00:00Daniel Paoliellodanpao@microsoft.com2025-05-15T23:38:46+00:00urn:sha1:6906b44e1c667705ce04626901a75d51f4910de3