Matt Arsenault fa848ccd09 R600: Remove a few more things from AMDILISelLowering
Try to keep all the setOperationActions for integer ops
together.

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@211001 91177308-0d34-0410-b5e6-96231b3b80d8
2014-06-15 21:08:58 +00:00
..
2014-06-09 08:36:53 +00:00
2014-06-10 19:18:24 +00:00
2014-06-10 19:18:28 +00:00
2014-06-10 19:00:20 +00:00
2014-06-10 19:00:20 +00:00
2014-06-06 01:20:28 +00:00
2014-05-02 15:41:47 +00:00
2014-05-02 15:41:47 +00:00
2014-06-05 00:15:55 +00:00
2014-06-15 21:08:54 +00:00
2014-05-09 16:42:19 +00:00
2014-06-09 16:36:31 +00:00
2014-06-09 16:36:31 +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.