Matt Arsenault 992b34c001 AMDGPU: Use s_addk_i32 / s_mulk_i32
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@266506 91177308-0d34-0410-b5e6-96231b3b80d8
2016-04-16 01:46:49 +00:00
..
2016-02-08 19:06:01 +00:00
2016-04-06 19:40:20 +00:00
2016-02-22 21:04:23 +00:00
2016-04-16 01:46:49 +00:00
2016-01-22 18:42:38 +00:00
2016-01-28 20:53:35 +00:00
2016-01-29 10:05:16 +00:00
2016-04-06 19:40:20 +00:00
2016-01-18 22:09:04 +00:00
2016-01-18 22:01:13 +00:00
2015-10-29 15:05:03 +00:00
2016-01-11 21:18:40 +00:00
2016-04-06 19:40:20 +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.