Matt Arsenault 20711b7bae R600/SI: Remove v_sub_f64 pseudo
The expansion code does the same thing. Since
the operands were not defined with the correct
types, this has the side effect of fixing operand
folding since the expanded pseudo would never use
SGPRs or inline immediates.

llvm-svn: 230072
2015-02-20 22:10:45 +00:00
..
2015-01-16 22:11:00 +00:00
2015-01-06 18:00:21 +00:00
2015-02-20 22:10:45 +00:00
2015-02-14 04:30:08 +00:00
2015-02-20 22:10:45 +00:00
2014-02-04 17:18:37 +00:00
2015-02-20 22:10:41 +00:00
2015-01-06 18:00:21 +00:00
2015-01-06 18:00:21 +00:00
2015-01-06 18:00:21 +00:00
2015-01-06 18:00:21 +00:00
2015-02-03 21:53:01 +00:00
2015-02-03 21:53:01 +00:00
2015-01-13 20:53:18 +00:00
2015-01-06 18:00:21 +00:00
2015-02-05 06:05:13 +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.