Files
clang-p2996/llvm/test/CodeGen/AMDGPU
Matt Arsenault 52d1b62a28 AMDGPU: Don't wait at end of block with a trivial successor
If there is only one successor, and that successor only
has one predecessor the wait can obviously be delayed until
uses or the end of the next block. This avoids code quality
regressions when there are trivial fallthrough blocks inserted
for structurization.

llvm-svn: 297251
2017-03-08 01:06:58 +00:00
..
2017-02-22 23:53:37 +00:00
2017-02-22 23:53:37 +00:00
2017-03-08 00:48:46 +00:00
2017-03-08 00:48:46 +00:00
2016-06-09 23:42:54 +00:00
2016-06-09 23:42:54 +00:00
2017-02-27 22:40:39 +00:00
2016-07-22 17:01:21 +00:00
2016-07-22 17:01:21 +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-06-02 19:54:26 +00:00
2017-02-15 17:19:50 +00:00
2017-02-27 19:35:42 +00:00
2017-03-08 00:48:46 +00:00
2016-08-02 22:25:04 +00:00
2016-12-22 03:21:45 +00:00
2017-02-22 00:27:34 +00:00
2017-02-27 22:40:39 +00:00
2017-02-22 00:27:34 +00:00
2016-11-10 16:02:37 +00:00
2017-01-30 18:11:38 +00:00
2017-02-27 22:40:39 +00:00
2017-01-30 18:11:38 +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.