Marek Olsak 91f22fbf4f AMDGPU/SI: Allow using SGPRs 96-101 on VI
Summary:
There is no point in setting SGPRS=104, because VI allocates SGPRs
in multiples of 16, so 104 -> 112. That enables us to use all 102 SGPRs
for general purposes.

Reviewers: tstellarAMD

Subscribers: qcolombet, arsenm, kzhuravl, wdng, nhaehnle, yaxunl, tony-tye

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

llvm-svn: 289260
2016-12-09 19:49:40 +00:00
..
2016-11-10 16:02:37 +00:00
2016-05-05 20:07:37 +00:00
2016-02-08 19:06:01 +00:00
2016-11-10 16:02:37 +00:00
2016-12-08 20:14:46 +00:00
2016-11-10 16:02:37 +00:00
2016-11-10 16:02:37 +00:00
2016-11-10 16:02:37 +00:00
2016-11-10 16:02:37 +00:00
2016-06-02 19:54:26 +00:00
2016-11-15 02:25:28 +00:00
2016-11-13 07:01:11 +00:00
2016-05-05 20:07:37 +00:00
2016-11-13 07:01:11 +00:00
2016-11-13 07:01:11 +00:00
2016-06-09 23:42:54 +00:00
2016-06-09 23:42:54 +00:00
2016-11-13 07:01:11 +00:00
2016-11-15 02:25:28 +00:00
2016-11-15 02:25:28 +00:00
2016-11-15 02:25:28 +00:00
2016-07-22 17:01:21 +00:00
2016-07-22 17:01:21 +00:00
2016-11-13 07:01:11 +00:00
2016-06-02 19:54:26 +00:00
2016-11-13 07:01:11 +00:00
2016-05-28 00:19:52 +00:00
2016-06-09 19:17:15 +00:00
2016-07-09 08:02:28 +00:00
2016-07-09 08:02:28 +00:00
2016-11-13 07:01:11 +00:00
2016-05-05 20:07:37 +00:00
2016-11-13 07:01:11 +00:00
2016-05-05 20:07:37 +00:00
2016-11-13 07:01:11 +00:00
2016-05-05 20:07:37 +00:00
2016-06-02 19:54:26 +00:00
2016-06-02 19:54:26 +00:00
2016-06-02 19:54:26 +00:00
2016-11-10 16:02:37 +00:00
2016-11-10 16:02:37 +00:00
2016-06-02 19:54:26 +00:00
2016-06-02 19:54:26 +00:00
2016-11-10 16:02:37 +00:00
2016-11-10 16:02:37 +00:00
2016-06-02 19:54:26 +00:00
2016-05-05 20:07:37 +00:00
2016-11-10 16:02:37 +00:00
2016-11-10 16:02:37 +00:00
2016-06-15 00:11:01 +00:00
2016-12-09 17:49:14 +00:00
2016-12-05 20:31:49 +00:00
2016-05-05 20:07:37 +00:00
2016-08-02 22:25:04 +00:00
2016-11-01 10:26:48 +00:00
2016-11-16 03:16:26 +00:00
2016-11-10 16:02:37 +00:00
2016-11-10 16:02:37 +00:00
2016-11-10 16:02:37 +00:00
2016-11-10 16:02:37 +00:00
2016-11-01 10:26:48 +00:00
2016-11-13 07:01:11 +00:00
2016-11-13 07:01:11 +00:00
2016-11-10 16:02:37 +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.