Files
rust/tests/ui
Matthias Krüger 27155e5ced Rollup merge of #135790 - wesleywiser:update_windows_gnu_debuginfokind, r=lqd
Update windows-gnu targets to set `DebuginfoKind::DWARF`

These targets have always used DWARF debuginfo and not CodeView/PDB debuginfo like the MSVC Windows targets. However, their target definitions claim to use `DebuginfoKind::PDB` probably to ensure that we do not try to allow the use of split-DWARF debuginfo.

This does not appear to be necessary since the targets set their supported split debug info to `Off`. I've looked at all of the uses of these properties and this patch does not appear to cause any functional changes in compiler behavior. I also added UI tests to attempt to validate there is no change in the behavior of these options on stable compilers.

cc ````@mati865```` since you mentioned this in #135739
cc ````@davidtwco```` for split-dwarf
2025-01-23 09:49:22 +01:00
..
2024-12-12 23:36:27 +00:00
2025-01-07 16:04:14 +01:00
2024-07-18 00:00:04 +00:00
2025-01-18 22:09:35 +00:00
2024-12-12 23:36:27 +00:00
2025-01-07 16:04:14 +01:00
2025-01-07 16:04:14 +01:00
2024-12-12 23:36:27 +00:00
2025-01-07 16:04:14 +01:00
2024-09-05 06:37:38 -04:00
2024-12-31 23:46:39 +08:00
2024-12-31 23:46:39 +08:00
2025-01-07 16:04:14 +01:00
2024-10-30 16:47:47 -07:00
2024-12-13 14:18:41 -08:00
2024-10-30 16:47:47 -07:00
2025-01-07 16:04:14 +01:00
2024-12-12 23:36:27 +00:00
2024-12-12 23:36:27 +00:00
2024-11-16 20:03:31 +00:00
2025-01-07 16:04:14 +01:00
2024-08-03 07:57:31 -04:00
2025-01-10 02:22:57 +01:00
2025-01-07 16:04:14 +01:00
2024-11-07 18:18:34 -08:00
2024-11-02 03:08:04 +00:00
2024-12-16 14:59:10 -05:00
2025-01-06 06:11:06 +00:00
2024-12-25 10:36:32 +01:00
2024-12-07 22:18:51 +00:00
2025-01-22 06:55:38 +00:00
2025-01-22 06:55:38 +00:00
2024-12-06 16:42:09 -05:00
2024-12-12 23:36:27 +00:00
2024-10-28 14:20:28 +11:00
2024-10-28 14:20:28 +11:00
2024-12-02 03:43:50 -07:00
2024-10-30 16:47:47 -07:00

UI Tests

This folder contains rustc's UI tests.

Test Directives (Headers)

Typically, a UI test will have some test directives / headers which are special comments that tell compiletest how to build and interpret a test.

As part of an ongoing effort to rewrite compiletest (see https://github.com/rust-lang/compiler-team/issues/536), a major change proposal to change legacy compiletest-style headers // <directive> to ui_test-style headers //@ <directive> was accepted (see https://github.com/rust-lang/compiler-team/issues/512.

An example directive is ignore-test. In legacy compiletest style, the header would be written as

// ignore-test

but in ui_test style, the header would be written as

//@ ignore-test

compiletest is changed to accept only //@ directives for UI tests (currently), and will reject and report an error if it encounters any comments // <content> that may be parsed as a legacy compiletest-style test header. To fix this, you should migrate to the ui_test-style header //@ <content>.