Files
archived-llvm/test/CodeGen/AMDGPU
Matt Arsenault a079dfc363 AMDGPU: Don't required structured CFG
The structured CFG is just an aid to inserting exec
mask modification instructions, once that is done
we don't really need it anymore. We also
do not analyze blocks with terminators that
modify exec, so this should only be impacting
true branches.

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@288744 91177308-0d34-0410-b5e6-96231b3b80d8
2016-12-06 01:02:51 +00:00
..
2016-11-10 16:02:37 +00:00
2016-11-10 16:02:37 +00:00
2016-05-05 20:07:37 +00:00
2016-02-08 19:06:01 +00:00
2016-11-10 16:02:37 +00:00
2016-11-10 16:02:37 +00:00
2016-11-10 16:02:37 +00:00
2016-11-10 16:02:37 +00:00
2016-11-10 16:02:37 +00:00
2016-06-02 19:54:26 +00:00
2016-11-15 02:25:28 +00:00
2016-11-13 07:01:11 +00:00
2016-05-05 20:07:37 +00:00
2016-11-13 07:01:11 +00:00
2016-11-13 07:01:11 +00:00
2016-06-09 23:42:54 +00:00
2016-06-09 23:42:54 +00:00
2016-11-13 07:01:11 +00:00
2016-11-15 02:25:28 +00:00
2016-11-15 02:25:28 +00:00
2016-11-15 02:25:28 +00:00
2016-07-22 17:01:21 +00:00
2016-07-22 17:01:21 +00:00
2016-11-13 07:01:11 +00:00
2016-06-02 19:54:26 +00:00
2016-11-13 07:01:11 +00:00
2016-05-28 00:19:52 +00:00
2016-06-09 19:17:15 +00:00
2016-07-09 08:02:28 +00:00
2016-07-09 08:02:28 +00:00
2016-11-13 07:01:11 +00:00
2016-05-05 20:07:37 +00:00
2016-11-13 07:01:11 +00:00
2016-05-05 20:07:37 +00:00
2016-11-13 07:01:11 +00:00
2016-05-05 20:07:37 +00:00
2016-06-02 19:54:26 +00:00
2016-06-02 19:54:26 +00:00
2016-06-02 19:54:26 +00:00
2016-11-10 16:02:37 +00:00
2016-11-10 16:02:37 +00:00
2016-06-02 19:54:26 +00:00
2016-06-02 19:54:26 +00:00
2016-11-10 16:02:37 +00:00
2016-11-10 16:02:37 +00:00
2016-06-02 19:54:26 +00:00
2016-05-05 20:07:37 +00:00
2016-11-10 16:02:37 +00:00
2016-11-10 16:02:37 +00:00
2016-06-15 00:11:01 +00:00
2016-05-05 20:07:37 +00:00
2016-12-05 20:31:49 +00:00
2016-05-05 20:07:37 +00:00
2016-08-02 22:25:04 +00:00
2016-11-01 10:26:48 +00:00
2016-11-16 03:16:26 +00:00
2016-11-10 16:02:37 +00:00
2016-11-10 16:02:37 +00:00
2016-11-10 16:02:37 +00:00
2016-11-10 16:02:37 +00:00
2016-11-01 10:26:48 +00:00
2016-11-13 07:01:11 +00:00
2016-11-13 07:01:11 +00:00
2016-11-10 16:02:37 +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.