mirror
/
rustc-dev-guide
mirror of https://github.com/rust-lang/rustc-dev-guide.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

compiletest: clarify that headers must be one header per line

This commit is contained in:
许杰友 Jieyou Xu (Joe) 2024-04-10 17:24:42 +01:00 committed by Tshepang Mbambo
parent 9fbba973ab
commit f70352388d
1 changed files with 5 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
src/tests/headers.md
View File

@ -5,7 +5,7 @@
Header commands are special comments that tell compiletest how to build and Header commands are special comments that tell compiletest how to build and
interpret a test. interpret a test.
They must appear before the Rust source in the test. They must appear before the Rust source in the test.
They may also appear in legacy Makefiles for They may also appear in `rmake.rs` or legacy Makefiles for
[run-make tests](compiletest.md#run-make-tests). [run-make tests](compiletest.md#run-make-tests).
They are normally put after the short comment that explains the point of this test. They are normally put after the short comment that explains the point of this test.
@ -27,6 +27,10 @@ fn main() {
Header commands can be standalone (like `//@ run-pass`) or take a value (like Header commands can be standalone (like `//@ run-pass`) or take a value (like
`//@ compile-flags: -C overflow-checks=off`). `//@ compile-flags: -C overflow-checks=off`).
Header commands are written with one header per line: you cannot write multiple
headers on the same line. For example, if you write `//@ only-x86 only-windows`
then `only-windows` is interpreted as a comment, not a separate directive.
## Header commands ## Header commands
The following is a list of header commands. The following is a list of header commands.