Files
clang-p2996/llvm/test/CodeGen/AMDGPU
Nikita Popov 3db93ac5d6 Reapply [ValueTracking] Support min/max selects in computeConstantRange()
Add support for min/max flavor selects in computeConstantRange(),
which allows us to fold comparisons of a min/max against a constant
in InstSimplify. This fixes an infinite InstCombine loop, with the
test case taken from D59378.

Relative to the previous iteration, this contains some adjustments for
AMDGPU med3 tests: The AMDGPU target runs InstSimplify prior to codegen,
which ends up constant folding some existing med3 tests after this
change. To preserve these tests a hidden -amdgpu-scalar-ir-passes option
is added, which allows disabling scalar IR passes (that use InstSimplify)
for testing purposes.

Differential Revision: https://reviews.llvm.org/D59506

llvm-svn: 357870
2019-04-07 17:22:16 +00:00
..
2019-03-29 17:35:56 +00:00
2019-02-08 11:59:48 +00:00
2019-03-19 15:50:24 +00:00
2019-03-21 12:01:21 +00:00
2019-03-29 17:35:56 +00:00
2019-03-29 17:35:56 +00:00
2019-03-29 17:35:56 +00:00
2019-03-29 17:35:56 +00:00
2019-03-29 17:35:56 +00:00
2019-03-12 21:02:54 +00:00
2019-03-12 21:02:54 +00:00
2018-08-31 22:43:36 +00:00
2019-03-21 12:01:21 +00:00
2019-03-19 15:50:24 +00:00
2019-03-19 15:50:24 +00:00
2018-06-27 15:33:33 +00:00
2018-06-27 15:33:33 +00:00
2019-03-21 12:01:21 +00:00
2018-12-07 17:46: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.