Files
clang-p2996/llvm/test/CodeGen/AMDGPU
Konstantin Zhuravlyov 941615e4c8 AMDGPU: Move isa version and EF_AMDGPU_MACH_* determination
into TargetParser.

Also switch away from target features to CPU string when
determining isa version. This fixes an issue when we
output wrong isa version in the object code when features
of a particular CPU are altered (i.e. gfx902 w/o xnack
used to result in gfx900).

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

llvm-svn: 341982
2018-09-11 18:56:51 +00:00
..
2018-05-29 19:35:53 +00:00
2018-06-12 18:02:46 +00:00
2018-07-31 13:25:23 +00:00
2018-08-03 18:27:52 +00:00
2018-07-31 13:25:23 +00:00
2018-04-30 19:08:16 +00:00
2018-08-29 16:31:18 +00:00
2017-11-28 23:40:12 +00:00
2018-08-31 22:43:36 +00:00
2018-08-31 22:43:36 +00:00
2018-06-27 15:33:33 +00:00
2018-06-27 15:33:33 +00:00
2018-08-08 16:58:33 +00:00
2018-05-07 13:21:26 +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.