Tom Stellard ad7ecc65b1 R600: Make sure to schedule AR register uses and defs in the same clause
Reviewed-by: vljn at ovi.com

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@183294 91177308-0d34-0410-b5e6-96231b3b80d8
2013-06-05 03:43:06 +00:00
..
2013-05-02 21:52:30 +00:00
2013-04-30 00:14:38 +00:00
2013-05-02 21:52:30 +00:00
2013-06-04 15:03:35 +00:00
2013-05-02 21:52:30 +00:00
2013-05-02 21:52:30 +00:00
2013-05-02 21:52:30 +00:00
2013-05-02 21:52:30 +00:00
2013-05-02 21:52:30 +00:00
2013-05-02 21:52:30 +00:00
2013-05-02 21:52:30 +00:00
2013-06-03 17:39:43 +00:00
2013-05-10 02:09:34 +00:00
2013-05-02 21:52:30 +00:00
2013-06-03 15:44:35 +00:00
2013-05-02 21:52:30 +00:00
2013-04-23 17:34:00 +00:00
2013-05-02 21:52:30 +00:00
2013-05-02 21:52:30 +00:00
2013-05-02 21:52:30 +00:00
2013-05-10 02:09:29 +00:00
2013-05-10 02:09:39 +00:00
2013-04-23 17:34:00 +00:00
2013-05-02 21:52:30 +00:00
2013-04-23 17:34:00 +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.