2014-09-19 23:02:20 +00:00
..
2014-08-06 20:27:55 +00:00
2014-07-15 20:18:31 +00:00
2014-09-10 21:44:27 +00:00
2014-08-06 20:27:55 +00:00
2014-09-05 14:26:54 +00:00
2014-08-29 16:01:14 +00:00
2014-09-15 16:48:01 +00:00
2014-09-03 23:24:35 +00:00
2014-09-02 21:45:50 +00:00
2014-07-15 21:44:37 +00:00
2014-07-15 21:44:37 +00:00
2014-07-21 14:01:10 +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.