blob: 96998bba28f24918afbbe316f96652a6887cc419 [file] [log] [blame]
Andrew Top61a84952019-04-30 15:07:33 -07001+==============================================================================+
2| How to organize the lit tests |
3+==============================================================================+
4
5- If you write a test for matching a single DAG opcode or intrinsic, it should
6 go in a file called {opcode_name,intrinsic_name}.ll (e.g. fadd.ll)
7
8- If you write a test that matches several DAG opcodes and checks for a single
9 ISA instruction, then that test should go in a file called {ISA_name}.ll (e.g.
10 bfi_int.ll
11
12- For all other tests, use your best judgement for organizing tests and naming
13 the files.
14
15+==============================================================================+
16| Naming conventions |
17+==============================================================================+
18
19- Use dash '-' and not underscore '_' to separate words in file names, unless
20 the file is named after a DAG opcode or ISA instruction that has an
21 underscore '_' in its name.