about summary refs log tree commit diff
path: root/tests/ui/check-cfg
AgeCommit message (Collapse)AuthorLines
2023-12-14Don't forget pure rustc target features in check-cfgUrgau-1/+4
2023-12-14Use all the known features in check-cfgUrgau-13/+24
2023-12-13Remove dangling check-cfg ui tests filesUrgau-249/+0
2023-12-13Add more suggestion to unexpected cfg names and valuesUrgau-74/+416
2023-12-11Rearrange `default_configuration` and `CheckCfg::fill_well_known`.Nicholas Nethercote-12/+12
There are comments saying these two functions should be kept in sync, but they have very different structures, process symbols in different orders, and there are some inconsistencies. This commit reorders them so they're both mostly processing symbols in alphabetical order, which makes cross-checking them a lot easier. The commit also adds some macros to factor out repetitive code patterns. Plus it adds `sanitizer_cfi_normalize_{integers,pointers}` to `fill_well_known`, which were missing. The commit also moves the handling of `sym::test` out of `build_configuration` into `default_configuration`, where all the other symbols are handled.
2023-12-09Avoid target_os and target_arch in some check-cfg testsUrgau-21/+4
as they unnecessarily clutter the diagnostic output and make the experience of adding a new target to the compiler more painful than it should be. target_os and target_arch are still being tested in the well-known-values.rs test, but in one place.
2023-12-09Strengthen well known check-cfg names and values testUrgau-56/+291
2023-12-05Remove deprecated --check-cfg names() and values() syntaxUrgau-172/+89
2023-11-21Improve diagnostic for unexpected feature config name from CargoUrgau-0/+25
2023-11-21Remove `feature` from the list of well known check-cfg nameUrgau-16/+51
2023-11-18Update --check-cfg tests that had old --cfg warningUrgau-83/+28
2023-10-27Better guard against wrong input with check-cfg any()Urgau-1/+7
2023-10-13MCP636: Adapt check-cfg tests to the new syntaxUrgau-121/+746
2023-10-12check-cfg: only print the list of expected names onceUrgau-24/+0
2023-10-12check-cfg: mention the unexpected name and value in the primary messageUrgau-56/+56
2023-10-12check-cfg: adjust expected names and values when usefulUrgau-1/+30
2023-09-21added support for GNU/HurdSamuel Thibault-2/+2
2023-08-14add `rustc_codegen_ssa` support for csky and correct some codeDirreke-1/+1
2023-07-26add aarch64-unknown-teeos target天命剑主-2/+2
Signed-off-by: 袁浩 <yuanhao34@huawei.com>
2023-07-18support for mips32r6 as a target_arch valuechenx97-1/+1
2023-07-18support for mips64r6 as a target_arch valuechenx97-1/+1
2023-05-06Fix --check-cfg bug with args order when parsingUrgau-0/+54
2023-05-05Improve check-cfg diagnostics (part 2)Urgau-35/+140
2023-05-05Improve check-cfg diagnostics (part 1)Urgau-27/+29
2023-04-04Initial support for loongarch64-unknown-linux-gnuzhaixiaojuan-1/+1
2023-03-09Honor current target when checking conditional compilation valuesUrgau-0/+46
This is fixed by simply using the currently registered target in the current session. We need to use it because of target json that are not by design included in the rustc list of targets.
2023-02-19Use restricted Damerau-Levenshtein algorithmJacob Pratt-1/+3
2023-01-11Move /src/test to /testsAlbert Larsan-0/+712