Jay Foad 2252cac694 [ANDGPU] getMemOperandsWithOffset: support BUF non-stack-access instructions with resource but no vaddr
Summary:
This enables clustering for many more BUF instructions.

Reviewers: rampitec, arsenm, nhaehnle

Subscribers: jvesely, wdng, hiraditya, kerbowa, llvm-commits

Tags: #llvm

Differential Revision: https://reviews.llvm.org/D73868
2020-02-03 22:49:30 +00:00
..
2019-07-11 21:19:33 +00:00
2019-09-25 18:50:34 +00:00
2019-10-07 10:57:41 +00:00
2020-01-06 17:21:51 -05:00
2019-07-01 17:17:45 +00:00
2019-07-09 18:10:06 +00:00
2019-07-08 19:03:38 +00:00
2019-07-11 21:19:33 +00:00
2019-07-08 19:03:38 +00:00
2019-07-11 21:19:33 +00:00
2020-01-09 15:56:36 -08:00
2019-07-15 17:50:31 +00:00
2019-07-24 19:40:13 +00:00
2019-07-27 14:32:23 +00:00
2020-01-09 15:56:36 -08:00
2020-01-09 15:56:36 -08:00
2020-01-09 15:56:36 -08:00
2020-01-09 15:56:36 -08:00
2020-01-09 15:56:36 -08:00
2020-01-12 22:44:51 -05:00
2020-01-09 15:56:36 -08: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.