Files
clang-p2996/llvm/test/CodeGen/AMDGPU
Stanislav Mekhanoshin 739174c4be [AMDGPU] Construct memory clauses before RA
Memory clauses are formed into bundles in presence of xnack.
Their source operands are marked as early-clobber.

This allows to allocate distinct source and destination registers
within a clause and prevent breaking the clause with s_nop in the
hazard recognizer.

Clauses are undone before post-RA scheduler to allow some rescheduling,
which will not break the clause since artificial edges are created in
the dag to keep memory operations together. Yet this allows a better
ILP in some cases.

Differential Revision: https://reviews.llvm.org/D47511

llvm-svn: 333691
2018-05-31 20:13:51 +00:00
..
2018-05-29 19:35:53 +00:00
2017-08-07 18:30:35 +00:00
2017-11-15 21:51:43 +00:00
2018-03-02 02:50:22 +00:00
2017-11-15 21:51:43 +00:00
2017-08-07 18:30:35 +00:00
2018-04-30 19:08:16 +00:00
2018-05-22 06:32:10 +00:00
2018-05-22 06:32:10 +00:00
2017-08-07 18:30:35 +00:00
2018-04-30 19:08:16 +00:00
2017-08-07 18:30:35 +00:00
2017-07-14 00:11:13 +00:00
2018-03-19 19:23:53 +00:00
2018-03-21 19:31:53 +00:00
2017-08-07 18:30:35 +00:00
2017-09-20 04:25:58 +00:00
2017-11-28 23:40:12 +00:00
2017-08-07 18:30:35 +00:00
2017-08-07 18:30:35 +00:00
2017-08-07 18:30:35 +00:00
2017-08-07 18:30:35 +00:00
2018-04-30 19:08:16 +00:00
2018-05-22 06:32:10 +00:00
2017-08-07 18:30:35 +00:00
2017-08-07 18:30:35 +00:00
2018-05-07 13:21:26 +00:00
2017-08-07 14:58:04 +00:00
2017-08-07 18:30:35 +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.