2020-04-17 11:59:39 -07:00
..
2020-02-14 09:53:22 -08:00
2019-09-25 18:50:34 +00:00
2020-03-20 11:01:51 -04:00
2020-03-30 13:23:56 -04: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-04-03 10:07:21 +01:00
2020-03-17 17:23:23 +01: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.