Tom Stellard d73d1062fe R600/SI: 64-bit and larger memory access must be at least 4-byte aligned
This is true for SI only. CI+ supports unaligned memory accesses,
but this requires driver support, so for now we disallow unaligned
accesses for all GCN targets.

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@227822 91177308-0d34-0410-b5e6-96231b3b80d8
2015-02-02 18:02:28 +00:00
..
2015-01-06 18:00:21 +00:00
2015-01-16 22:11: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-13 20:53:18 +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.