Matt Arsenault c305513cc2 AMDGPU: Fix assert with indirect call with known required inputs
The attributor can determine that some indirect calls do not require
special inputs. The special inputs will still be present in the ABI,
so we need to allocate the registers and pass undefs.
2021-09-13 22:54:11 -04:00
..
2021-02-17 16:01:32 -08:00
2021-02-17 16:01:32 -08:00
2021-02-17 16:01:32 -08:00
2021-07-25 14:05:08 +01:00
2021-02-17 16:01:32 -08:00
2021-02-17 16:01:32 -08:00
2021-02-17 16:01:32 -08:00
2021-01-21 10:51:36 -05:00
2021-02-17 16:01:32 -08:00
2021-08-25 09:50:59 -07:00
2021-02-17 16:01:32 -08:00
2021-02-17 16:01:32 -08:00
2021-03-15 21:44:15 +09: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.