2013-09-30 18:17:55 +00:00
..
2013-07-23 01:48:18 +00:00
2013-06-04 15:03:35 +00:00
2013-08-10 10:38:47 +00:00
2013-07-12 18:15:13 +00:00
2013-08-16 23:51:29 +00:00
2013-08-16 23:51:33 +00:00
2013-06-25 13:55:29 +00:00
2013-05-02 21:52:30 +00:00
2013-05-02 21:52:30 +00:00
2013-04-23 17:34:00 +00:00
2013-07-15 19:00:09 +00:00
2013-09-05 19:41: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.