Tom Stellard ad52f4f70c R600/SI: Fix implementation of isInlineConstant() used by the verifier
The type of the immediates should not matter as long as the encoding is
equivalent to the encoding of one of the legal inline constants.

Tested-by: Michel Dänzer <michel.daenzer@amd.com>

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@204056 91177308-0d34-0410-b5e6-96231b3b80d8
2014-03-17 17:03:52 +00:00
..
2014-02-25 21:36:18 +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
2014-01-11 21:06:00 +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
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-01-11 21:06:00 +00:00
2014-03-07 20:12:33 +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

+==============================================================================+
| 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.