Marek Olsak 438e1f2ad8 R600/SI: Use i32 vectors for resources and samplers
This affects new intrinsics only.

What surprises me is that v32i8 still works.

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@212831 91177308-0d34-0410-b5e6-96231b3b80d8
2014-07-11 17:11:52 +00:00
..
2014-07-02 20:53:54 +00:00
2014-06-09 08:36:53 +00:00
2014-06-18 17:57:29 +00:00
2014-06-18 17:57:29 +00:00
2014-06-10 19:00:20 +00:00
2014-06-10 19:00:20 +00:00
2014-06-26 01:28:05 +00:00
2014-06-18 22:03:45 +00:00
2014-06-20 17:06:05 +00:00
2014-06-06 01:20:28 +00:00
2014-06-20 17:06:05 +00:00
2014-06-20 17:06:07 +00:00
2014-07-02 20:53:54 +00:00
2014-07-02 20:53:54 +00:00
2014-06-05 00:15:55 +00:00
2014-06-15 21:08:54 +00:00
2014-06-18 12:27:13 +00:00
2014-06-18 12:27:17 +00:00
2014-06-18 12:27:15 +00:00
2014-06-24 23:33:04 +00:00
2014-06-23 18:00:38 +00:00
2014-06-22 21:42:58 +00:00
2014-06-20 17:05:57 +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.