Files
clang-p2996/llvm/test/CodeGen/AMDGPU
Tom Stellard b7f19e6d1e AMDGPU/GlobalISel: Legalize G_INSERT
Reviewers: arsenm

Subscribers: kzhuravl, wdng, nhaehnle, yaxunl, rovka, kristof.beyls, dstuttard, tpr, t-tye, llvm-commits

Differential Revision: https://reviews.llvm.org/D49601

llvm-svn: 337798
2018-07-24 02:19:20 +00:00
..
2018-05-29 19:35:53 +00:00
2017-11-15 21:51:43 +00:00
2018-06-12 18:02:46 +00:00
2018-05-22 06:32:10 +00:00
2018-05-22 06:32:10 +00:00
2018-04-30 19:08:16 +00:00
2017-11-28 23:40:12 +00:00
2018-06-15 15:15:46 +00:00
2018-04-30 19:08:16 +00:00
2018-06-27 15:33:33 +00:00
2018-06-27 15:33:33 +00:00
2018-06-27 15:33:33 +00:00
2018-05-07 13:21:26 +00:00
2018-06-27 15:33:33 +00:00
2018-06-27 15:33:33 +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.