| Age | Commit message (Collapse) | Author | Lines | |
|---|---|---|---|---|
| 2023-12-14 | Don't forget pure rustc target features in check-cfg | Urgau | -1/+4 | |
| 2023-12-14 | Use all the known features in check-cfg | Urgau | -13/+24 | |
| 2023-12-13 | Remove dangling check-cfg ui tests files | Urgau | -249/+0 | |
| 2023-12-13 | Add more suggestion to unexpected cfg names and values | Urgau | -74/+416 | |
| 2023-12-11 | Rearrange `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-09 | Avoid target_os and target_arch in some check-cfg tests | Urgau | -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-09 | Strengthen well known check-cfg names and values test | Urgau | -56/+291 | |
| 2023-12-05 | Remove deprecated --check-cfg names() and values() syntax | Urgau | -172/+89 | |
| 2023-11-21 | Improve diagnostic for unexpected feature config name from Cargo | Urgau | -0/+25 | |
| 2023-11-21 | Remove `feature` from the list of well known check-cfg name | Urgau | -16/+51 | |
| 2023-11-18 | Update --check-cfg tests that had old --cfg warning | Urgau | -83/+28 | |
| 2023-10-27 | Better guard against wrong input with check-cfg any() | Urgau | -1/+7 | |
| 2023-10-13 | MCP636: Adapt check-cfg tests to the new syntax | Urgau | -121/+746 | |
| 2023-10-12 | check-cfg: only print the list of expected names once | Urgau | -24/+0 | |
| 2023-10-12 | check-cfg: mention the unexpected name and value in the primary message | Urgau | -56/+56 | |
| 2023-10-12 | check-cfg: adjust expected names and values when useful | Urgau | -1/+30 | |
| 2023-09-21 | added support for GNU/Hurd | Samuel Thibault | -2/+2 | |
| 2023-08-14 | add `rustc_codegen_ssa` support for csky and correct some code | Dirreke | -1/+1 | |
| 2023-07-26 | add aarch64-unknown-teeos target | 天命剑主 | -2/+2 | |
| Signed-off-by: 袁浩 <yuanhao34@huawei.com> | ||||
| 2023-07-18 | support for mips32r6 as a target_arch value | chenx97 | -1/+1 | |
| 2023-07-18 | support for mips64r6 as a target_arch value | chenx97 | -1/+1 | |
| 2023-05-06 | Fix --check-cfg bug with args order when parsing | Urgau | -0/+54 | |
| 2023-05-05 | Improve check-cfg diagnostics (part 2) | Urgau | -35/+140 | |
| 2023-05-05 | Improve check-cfg diagnostics (part 1) | Urgau | -27/+29 | |
| 2023-04-04 | Initial support for loongarch64-unknown-linux-gnu | zhaixiaojuan | -1/+1 | |
| 2023-03-09 | Honor current target when checking conditional compilation values | Urgau | -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-19 | Use restricted Damerau-Levenshtein algorithm | Jacob Pratt | -1/+3 | |
| 2023-01-11 | Move /src/test to /tests | Albert Larsan | -0/+712 | |
