Tom Stellard 99d8179a9b R600: Initialize AMDGPUMachineFunction::ShaderType to ShaderType::COMPUTE
We need to intialize this to something and since clang does not set
the shader type attribute and clang is used only for compute shaders,
initializing it to COMPUTE seems like the best choice.

Reviewed-by: Christian König <christian.koenig@amd.com>

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@180620 91177308-0d34-0410-b5e6-96231b3b80d8
2013-04-26 18:32:24 +00:00
..
2012-12-11 21:25:42 +00:00
2012-12-11 21:25:42 +00:00
2012-12-11 21:25:42 +00:00
2012-12-11 21:25:42 +00:00
2012-12-11 21:25:42 +00:00
2012-12-11 21:25:42 +00:00
2012-12-11 21:25:42 +00:00
2013-03-09 18:25:40 +00:00
2012-12-11 21:25:42 +00:00
2012-12-11 21:25:42 +00:00
2012-12-11 21:25:42 +00:00
2012-12-11 21:25:42 +00:00
2012-12-11 21:25:42 +00:00
2013-04-23 17:34:00 +00:00
2013-04-23 17:34:00 +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.