Tom Stellard eb643b9b37 R600: Improve support for < 32-bit loads
Reviewed-by: Vincent Lejeune <vljn at ovi.com>

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@186921 91177308-0d34-0410-b5e6-96231b3b80d8
2013-07-23 01:48:35 +00:00
..
2013-07-23 01:48:18 +00:00
2013-07-23 01:48:18 +00:00
2013-07-23 01:47:46 +00:00
2013-07-12 18:15:13 +00:00
2013-06-25 13:55:29 +00:00
2013-07-23 01:48:18 +00:00
2013-07-15 19:00:09 +00:00
2013-07-18 21:43:42 +00:00
2013-07-18 21:43:53 +00:00
2013-06-25 13:55:52 +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.