Files
rust/tests/ui
Kajetan Puchalski 4f847bd326 rustc_target: Add various aarch64 features
Add various aarch64 features already supported by LLVM and Linux.

The features are marked as unstable using a newly added symbol, i.e.
aarch64_unstable_target_feature.

Additionally include some comment fixes to ensure consistency of
feature names with the Arm ARM and support for architecture version
target features up to v9.5a.

This commit adds compiler support for the following features:

- FEAT_CSSC
- FEAT_ECV
- FEAT_FAMINMAX
- FEAT_FLAGM2
- FEAT_FP8
- FEAT_FP8DOT2
- FEAT_FP8DOT4
- FEAT_FP8FMA
- FEAT_FPMR
- FEAT_HBC
- FEAT_LSE128
- FEAT_LSE2
- FEAT_LUT
- FEAT_MOPS
- FEAT_LRCPC3
- FEAT_SVE_B16B16
- FEAT_SVE2p1
- FEAT_WFxT
2024-08-27 11:11:47 +01:00
..
2024-07-28 03:11:54 +08:00
2024-07-29 21:47:19 -04:00
2024-08-23 16:09:56 -07:00
2024-08-10 12:07:17 +02:00
2024-08-09 22:02:23 -04:00
2024-08-10 12:07:17 +02:00
2024-08-02 11:34:54 +00:00
2024-08-08 00:41:39 +08:00
2024-08-18 19:46:53 +02:00
2024-08-18 19:46:53 +02:00
2024-08-10 12:07:17 +02:00
2024-08-17 12:43:25 -04:00
2024-08-18 19:46:53 +02:00
2024-08-02 11:34:54 +00:00
2024-08-12 13:00:12 +10:00
2024-08-02 11:34:54 +00:00
2024-08-03 07:57:31 -04:00
2024-08-18 19:46:53 +02:00
2024-08-17 12:43:25 -04:00
2024-08-18 19:46:53 +02:00
2024-08-18 19:46:53 +02: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 intepret a test.

As part of an on-going 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 an legacy compiletest-style test header. To fix this, you should migrate to the ui_test-style header //@ <content>.