2014-04-22 16:42:00 +00:00
..
2014-03-27 17:23:31 +00:00
2014-01-23 18:49:33 +00:00
2014-02-04 07:12:38 +00:00
2014-02-04 07:12:38 +00:00
2014-02-04 07:12:38 +00:00
2013-12-10 21:11:55 +00:00
2014-01-11 21:06:00 +00:00
2014-02-04 17:18:37 +00:00
2014-04-17 17:06:37 +00:00
2013-10-29 16:37:20 +00:00
2013-12-20 05:11:55 +00:00
2013-12-14 00:38:04 +00:00
2014-04-15 22:28:39 +00:00
2014-04-17 02:03:08 +00:00
2013-11-06 17:36:04 +00:00
2014-01-11 21:06:00 +00:00
2013-10-13 17:56:28 +00:00
2014-04-09 07:16:16 +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.