about summary refs log tree commit diff
path: root/tests/ui/abi/debug.rs
AgeCommit message (Collapse)AuthorLines
2025-08-21Fix the ABI parameter inconsistency issue in debug.rs for LoongArch64WANG Rui-1/+4
2025-07-04Fix tests/ui/abi/debug.rs to cross-compile for riscv64Jubilee Young-1/+2
2025-07-04Fixed the ABI parameter inconsistency issue in debug.rs for the riscv64 ↵YingkaiLi-VM-0/+3
architecture.
2025-07-03minicore: use core's `diagnostic::on_unimplemented` messagesFolkert de Vries-3/+13
2025-04-17Replace infallible `name_or_empty` methods with fallible `name` methods.Nicholas Nethercote-1/+1
I'm removing empty identifiers everywhere, because in practice they always mean "no identifier" rather than "empty identifier". (An empty identifier is impossible.) It's better to use `Option` to mean "no identifier" because you then can't forget about the "no identifier" possibility. Some specifics: - When testing an attribute for a single name, the commit uses the `has_name` method. - When testing an attribute for multiple names, the commit uses the new `has_any_name` method. - When using `match` on an attribute, the match arms now have `Some` on them. In the tests, we now avoid printing empty identifiers by not printing the identifier in the `error:` line at all, instead letting the carets point out the problem.
2025-04-17Augment some tests involving attributes.Nicholas Nethercote-0/+3
This shows places where the use of `name_or_empty` causes problems, i.e. we print empty identifiers in error messages: ``` error: unrecognized field name `` error: `` isn't a valid `#[macro_export]` argument `#[no_sanitize()]` should be applied to a function ``` (The last one is about an attribute `#[no_sanitize("address")]`.) The next commit will fix these.
2025-01-10adjust UI testsThe 8472-0/+1
2024-12-27Remove the `-test` suffix from normalize directivesZalathar-5/+5
2024-07-11Always use a colon in `//@ normalize-*:` headersZalathar-5/+5
2024-02-16[AUTO-GENERATED] Migrate ui tests from `//` to `//@` directives许杰友 Jieyou Xu (Joe)-6/+6
2023-09-15special case `TyAndLayout` debug implBoxy-1/+0
2023-09-11Disentangle `Debug` and `Display` for `Ty`.Nicholas Nethercote-0/+1
The `Debug` impl for `Ty` just calls the `Display` impl for `Ty`. This is surprising and annoying. In particular, it means `Debug` doesn't show as much information as `Debug` for `TyKind` does. And `Debug` is used in some user-facing error messages, which seems bad. This commit changes the `Debug` impl for `Ty` to call the `Debug` impl for `TyKind`. It also does a number of follow-up changes to preserve existing output, many of which involve inserting `with_no_trimmed_paths!` calls. It also adds `Display` impls for `UserType` and `Canonical`. Some tests have changes to expected output: - Those that use the `rustc_abi(debug)` attribute. - Those that use the `EMIT_MIR` annotation. In each case the output is slightly uglier than before. This isn't ideal, but it's pretty weird (particularly for the attribute) that the output is using `Debug` in the first place. They're fairly obscure attributes (I hadn't heard of them) so I'm not worried by this. For `async-is-unwindsafe.stderr`, there is one line that now lacks a full path. This is a consistency improvement, because all the other mentions of `Context` in this test lack a path.
2023-09-09rustc_layout, rustc_abi: make sure the types are well-formedRalf Jung-0/+3
2023-09-08also ensure that size and alignment are the sameRalf Jung-0/+3
2023-09-08accept some differences for rustc_abi(assert_eq), so that we can test more ↵Ralf Jung-0/+7
things to be compatible
2023-09-07add support for rustc_abi(assert_eq) and use it to test some ↵Ralf Jung-0/+6
repr(transparent) cases
2023-09-06rustc_layout/abi: error when attribute is applied to the wrong thingRalf Jung-1/+10
2023-09-06rustc_abi: also support debugging function pointersRalf Jung-0/+2
2023-08-27add rustc_abi debugging attributeRalf Jung-0/+23