Files
clang-p2996/llvm/test/CodeGen/AMDGPU
2021-09-02 17:39:17 -07:00
..
2021-02-17 16:01:32 -08:00
2019-05-08 22:09:57 +00:00
2017-08-07 18:30:35 +00:00
2017-08-07 18:30:35 +00:00
2020-08-09 20:50:30 +02:00
2021-02-17 16:01:32 -08:00
2021-07-25 14:05:08 +01:00
2020-06-15 16:18:05 -07:00
2019-03-19 15:50:24 +00:00
2019-04-26 16:37:51 +00:00
2021-02-17 16:01:32 -08:00
2019-05-03 15:37:07 +00:00
2015-06-13 03:28:10 +00:00
2021-02-17 16:01:32 -08:00
2021-08-25 09:50:59 -07:00
2018-06-27 15:33:33 +00:00
2020-08-09 20:50:30 +02:00
2019-06-20 15:08:34 +00:00

+==============================================================================+
| How to organize the lit tests                                                |
+==============================================================================+

- If you write a test for matching a single DAG opcode or intrinsic, it should
  go in a file called {opcode_name,intrinsic_name}.ll (e.g. fadd.ll)

- If you write a test that matches several DAG opcodes and checks for a single
  ISA instruction, then that test should go in a file called {ISA_name}.ll (e.g.
  bfi_int.ll

- For all other tests, use your best judgement for organizing tests and naming
  the files.

+==============================================================================+
| Naming conventions                                                           |
+==============================================================================+

- Use dash '-' and not underscore '_' to separate words in file names, unless
  the file is named after a DAG opcode or ISA instruction that has an
  underscore '_' in its name.