Commit Graph

28 Commits

Author SHA1 Message Date
Urgau c355040a5c Don't forget pure rustc target features in check-cfg 2023-12-14 14:50:32 +01:00
Urgau acac133997 Use all the known features in check-cfg 2023-12-14 14:49:42 +01:00
Urgau f6617d050d Remove dangling check-cfg ui tests files 2023-12-13 17:48:04 +01:00
Urgau 5345a166fe Add more suggestion to unexpected cfg names and values 2023-12-13 17:48:04 +01:00
Nicholas Nethercote 22b534de4f Rearrange default_configuration and CheckCfg::fill_well_known.
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-11 10:04:47 +11:00
Urgau 4c1671674e Avoid target_os and target_arch in some check-cfg tests
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-09 11:59:46 +01:00
Urgau bba9862b95 Strengthen well known check-cfg names and values test 2023-12-09 11:59:46 +01:00
Urgau 3f0369e0f2 Remove deprecated --check-cfg names() and values() syntax 2023-12-05 13:25:11 +01:00
Urgau 1c37997fa7 Improve diagnostic for unexpected feature config name from Cargo 2023-11-21 19:06:58 +01:00
Urgau 9f15acec47 Remove feature from the list of well known check-cfg name 2023-11-21 19:06:58 +01:00
Urgau a5658e6de8 Update --check-cfg tests that had old --cfg warning 2023-11-18 12:21:58 +01:00
Urgau 84a1a689cc Better guard against wrong input with check-cfg any() 2023-10-27 12:02:54 +02:00
Urgau fc78d78988 MCP636: Adapt check-cfg tests to the new syntax 2023-10-13 13:51:03 +02:00
Urgau 001a65c4b0 check-cfg: only print the list of expected names once 2023-10-12 18:39:35 +02:00
Urgau dcfc484b09 check-cfg: mention the unexpected name and value in the primary message 2023-10-12 18:39:04 +02:00
Urgau 72815dc08f check-cfg: adjust expected names and values when useful 2023-10-12 18:39:04 +02:00
Samuel Thibault dcea7709f2 added support for GNU/Hurd 2023-09-21 17:31:25 +02:00
Dirreke 8c51e28bd5 add rustc_codegen_ssa support for csky and correct some code 2023-08-14 23:02:36 +08:00
天命剑主 72dd53c8e5 add aarch64-unknown-teeos target
Signed-off-by: 袁浩 <yuanhao34@huawei.com>
2023-07-26 21:39:40 +08:00
chenx97 d3727148a0 support for mips32r6 as a target_arch value 2023-07-18 18:58:18 +08:00
chenx97 c6e03cd951 support for mips64r6 as a target_arch value 2023-07-18 18:58:18 +08:00
Urgau f4ca42f573 Fix --check-cfg bug with args order when parsing 2023-05-06 18:40:47 +02:00
Urgau 53647845b9 Improve check-cfg diagnostics (part 2) 2023-05-05 13:06:48 +02:00
Urgau a5f8dba4cd Improve check-cfg diagnostics (part 1) 2023-05-05 13:06:48 +02:00
zhaixiaojuan ad26dab27c Initial support for loongarch64-unknown-linux-gnu 2023-04-04 17:05:07 +08:00
Urgau 3455d66041 Honor current target when checking conditional compilation values
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-03-09 21:55:00 +01:00
Jacob Pratt ff052eec80 Use restricted Damerau-Levenshtein algorithm 2023-02-19 03:46:03 +00:00
Albert Larsan cf2dff2b1e Move /src/test to /tests 2023-01-11 09:32:08 +00:00