Tom Stellard c4a246996d R600: Fix R600ControlFlowFinalizer not considering VTX_READ 128 bit dst reg
Patch by: Vincent Lejeune

https://bugs.freedesktop.org/show_bug.cgi?id=64877

NOTE: This is a candidate for the 3.3 branch.


Merged from r182600
Author: Tom Stellard <thomas.stellard@amd.com>
Date:   Thu May 23 18:26:42 2013 +0000

git-svn-id: https://llvm.org/svn/llvm-project/llvm/branches/release_33@185868 91177308-0d34-0410-b5e6-96231b3b80d8
2013-07-08 21:20:22 +00:00
..
2013-05-02 21:52:30 +00:00
2013-04-30 00:14:38 +00:00
2013-05-02 21:52:30 +00:00
2013-05-16 00:27:57 +00:00
2013-05-02 21:52:30 +00:00
2013-05-02 21:52:30 +00:00
2013-05-02 21:52:30 +00:00
2013-05-02 21:52:30 +00:00
2013-05-02 21:52:30 +00:00
2013-05-02 21:52:30 +00:00
2013-05-02 21:52:30 +00:00
2013-05-02 21:52:30 +00:00
2013-05-02 21:52:30 +00:00
2013-05-02 21:52:30 +00:00
2013-05-02 21:52:30 +00:00
2013-05-02 21:52:30 +00:00
2013-05-02 21:52:30 +00:00
2013-05-02 21:52:30 +00:00
2013-05-02 21:52:30 +00:00
2013-05-02 21:52:30 +00:00
2013-05-02 21:52:30 +00:00
2013-05-16 00:27:29 +00:00
2013-05-02 21:52:30 +00:00
2013-05-17 23:36:26 +00:00
2013-05-02 21:52:30 +00:00
2013-05-02 21:52:30 +00:00
2013-05-02 21:52:30 +00:00
2013-05-02 21:52:30 +00:00
2013-05-16 00:27:17 +00:00
2013-05-16 00:27:42 +00:00
2013-05-02 21:52:30 +00:00
2013-05-16 00:27:04 +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.