Files
clang-p2996/llvm/test/CodeGen/AMDGPU
Yaxun Liu 30e4608cca CodeGen: Fix SelectionDAGISel::LowerArguments for sret addr space
SelectionDAGISel::LowerArguments assumes sret addr space is 0, which is
not true for amdgcn---amdgiz target.

This patch fixes that.

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

llvm-svn: 319630
2017-12-03 03:31:45 +00:00
..
2017-08-07 18:30:35 +00:00
2017-11-28 23:40:12 +00:00
2017-11-15 21:51:43 +00:00
2017-11-15 21:51:43 +00:00
2017-08-07 18:30:35 +00:00
2017-07-21 21:19:23 +00:00
2017-08-07 18:30:35 +00:00
2017-08-07 18:30:35 +00:00
2017-08-07 14:58:04 +00:00
2017-08-07 14:58:04 +00:00
2017-08-07 18:30:35 +00:00
2017-08-07 14:58:04 +00:00
2017-07-14 00:11:13 +00:00
2017-11-17 04:18:24 +00:00
2017-08-07 18:30:35 +00:00
2017-08-07 18:30:35 +00:00
2017-09-20 04:25:58 +00:00
2017-11-28 23:40:12 +00:00
2017-08-07 18:30:35 +00:00
2017-08-07 18:30:35 +00:00
2017-08-07 18:30:35 +00:00
2017-08-07 18:30:35 +00:00
2017-08-07 18:30:35 +00:00
2017-11-15 21:51:43 +00:00
2017-05-19 17:25:20 +00:00
2017-08-07 14:58:04 +00:00
2017-08-07 18:30:35 +00:00
2017-08-07 18:30:35 +00:00
2017-06-28 21:38:50 +00:00
2017-06-28 21:38:50 +00:00
2017-06-28 21:38:50 +00:00
2017-06-28 21:38:50 +00:00
2017-08-07 18:30:35 +00:00
2017-07-21 21:19:23 +00:00
2017-07-14 00:11:13 +00:00
2017-08-07 14:58:04 +00:00
2017-08-07 18:30:35 +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.