Matt Arsenault aac455af99 R600: Fix asserts related to constant initializers
This would assert if a constant address space was extern
and therefore didn't have an initializer. If the initializer
was undef, it would hit the unreachable unhandled initializer case.

An extern global should never really occur since we don't have
machine linking, but bugpoint likes to remove initializers.

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@210967 91177308-0d34-0410-b5e6-96231b3b80d8
2014-06-14 04:26:05 +00:00
..
2014-06-09 08:36:53 +00:00
2014-01-23 18:49:33 +00:00
2013-06-04 15:03:35 +00:00
2014-06-10 19:18:24 +00:00
2014-06-10 19:18:28 +00:00
2014-06-10 19:00:20 +00:00
2014-06-10 19:00:20 +00:00
2014-02-04 07:12:38 +00:00
2013-12-10 21:11:55 +00:00
2014-06-06 01:20:28 +00:00
2014-05-02 15:41:47 +00:00
2014-02-04 17:18:37 +00:00
2014-05-02 15:41:47 +00:00
2013-12-20 05:11:55 +00:00
2013-12-14 00:38:04 +00:00
2014-06-05 00:15:55 +00:00
2014-05-09 16:42:19 +00:00
2014-06-09 16:36:31 +00:00
2013-11-06 17:36:04 +00:00
2014-01-11 21:06:00 +00:00
2013-10-13 17:56:28 +00:00
2014-06-09 16:36:31 +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.