Files
llvm/test/CodeGen/AMDGPU
Matt Arsenault eaf2a8e1e8 AMDGPU: Disable stack realignment for kernels
This is something of a workaround, and the state of stack realignment
controls is kind of a mess. Ideally, we would be able to specify the
stack is infinitely aligned on entry to a kernel.

TargetFrameLowering provides multiple controls which apply at
different points. The StackRealignable field is used during
SelectionDAG, and for some reason distinct from this
hook. StackAlignment is a single field not dependent on the
function. It would probably be better to make that dependent on the
calling convention, and the maximum value for kernels.

Currently this doesn't really change anything, since the frame
lowering mostly does its own thing. This helps avoid regressions in a
future change which will rely more heavily on hasFP.

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@362447 91177308-0d34-0410-b5e6-96231b3b80d8
2019-06-03 21:33:22 +00:00
..
2019-05-10 00:09:01 +00:00
2019-05-10 00:09:01 +00:00
2019-05-08 22:09:57 +00:00
2019-05-10 00:09:01 +00:00
2019-03-29 17:35:56 +00:00
2017-08-07 18:30:35 +00:00
2019-04-09 16:13:53 +00:00
2019-02-08 11:59:48 +00:00
2017-08-07 18:30:35 +00:00
2019-05-13 19:30:06 +00:00
2019-03-19 15:50:24 +00:00
2018-04-30 19:08:16 +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
2017-08-07 18:30:35 +00:00
2019-03-12 21:02:54 +00:00
2019-03-12 21:02:54 +00:00
2017-08-07 18:30:35 +00:00
2018-08-31 22:43:36 +00:00
2017-08-07 18:30:35 +00:00
2019-03-21 12:01:21 +00:00
2019-03-19 15:50:24 +00:00
2019-04-26 16:37:51 +00:00
2019-03-19 15:50:24 +00:00
2019-05-10 00:09:01 +00:00
2019-05-08 22:09:57 +00:00
2019-05-03 15:37:07 +00:00
2018-06-27 15:33:33 +00:00
2018-06-27 15:33:33 +00:00
2017-08-07 18:30:35 +00:00
2017-08-07 18:30:35 +00:00
2019-05-10 00:09:01 +00:00
2019-05-10 00:09:01 +00:00
2019-05-13 19:30:06 +00:00
2019-05-03 15:37:07 +00:00
2017-08-07 18:30:35 +00:00
2019-05-13 19:30:06 +00:00
2019-03-21 12:01:21 +00:00
2019-05-10 00:09:01 +00:00
2019-05-10 00:09:01 +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.