Tom Stellard 1f996fa36b R600/SI: Add a stub GCNTargetMachine
This is equivalent to the AMDGPUTargetMachine now, but it is the
starting point for separating R600 and GCN functionality into separate
targets.

It is recommened that users start using the gcn triple for GCN-based
GPUs, because using the r600 triple for these GPUs will be deprecated in
the future.

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@225277 91177308-0d34-0410-b5e6-96231b3b80d8
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
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
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
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.