Files
archived-llvm/test/CodeGen/R600
Tom Stellard d275e025d2 R600/SI: Use RegisterOperands to specify which operands can accept immediates
There are some operands which can take either immediates or registers
and we were previously using different register class to distinguish
between operands that could take immediates and those that could not.

This patch switches to using RegisterOperands which should simplify the
backend by reducing the number of register classes and also make it
easier to implement the assembler.

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@225662 91177308-0d34-0410-b5e6-96231b3b80d8
2015-01-12 19:33:18 +00:00
..
2015-01-06 18:00:21 +00:00
2015-01-06 18:00:21 +00:00
2015-01-06 18:00:21 +00:00
2015-01-06 18:00:21 +00:00
2015-01-06 18:00:21 +00:00
2015-01-06 18:00:21 +00:00
2015-01-06 18:00:21 +00:00
2015-01-06 18:00:21 +00:00
2015-01-06 18:00:21 +00:00
2015-01-06 18:00:21 +00:00
2015-01-06 18:00:21 +00:00
2015-01-06 18:00:21 +00:00
2015-01-06 18:00:21 +00:00
2015-01-06 18:00:21 +00:00
2015-01-06 18:00:21 +00:00
2015-01-06 18:00:21 +00:00
2015-01-06 18:00:21 +00:00
2015-01-06 18:00:21 +00:00
2015-01-06 18:00:21 +00:00
2015-01-06 18:00:21 +00:00
2015-01-06 18:00:21 +00:00
2015-01-06 18:00:21 +00:00
2015-01-06 18:00:21 +00:00
2015-01-06 18:00:21 +00:00
2015-01-06 18:00:21 +00:00
2015-01-06 18:00:21 +00:00
2015-01-06 18:00:21 +00:00
2015-01-06 18:00:21 +00:00
2014-12-03 04:08:00 +00:00
2014-02-04 17:18:37 +00:00
2015-01-06 18:00:21 +00:00
2015-01-06 18:00:21 +00:00
2015-01-06 18:00:21 +00:00
2015-01-06 18:00:21 +00:00
2015-01-06 18:00:21 +00:00
2015-01-06 18:00:21 +00:00
2015-01-06 18:00:21 +00:00
2015-01-06 18:00:21 +00:00
2015-01-06 18:00:21 +00:00
2015-01-06 18:00:21 +00:00
2015-01-06 18:00:21 +00:00
2015-01-06 18:00:21 +00:00
2015-01-06 18:00:21 +00:00
2015-01-06 18:00:21 +00:00
2015-01-06 18:00:21 +00:00
2015-01-06 18:00:21 +00:00
2015-01-06 18:00:21 +00:00
2015-01-06 18:00:21 +00:00
2015-01-06 18:00:21 +00:00
2015-01-06 18:00:21 +00:00
2015-01-06 18:00:21 +00:00
2015-01-06 18:00:21 +00:00
2015-01-06 18:00:21 +00:00
2015-01-06 18:00:21 +00:00
2015-01-06 18:00:21 +00:00
2015-01-06 18:00:21 +00:00
2015-01-06 18:00:21 +00:00
2015-01-06 18:00:21 +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.