llvm-project

Commit Graph

Author	SHA1	Message	Date
Philip Pfaffe	f6f8b25e58	[NFC] In GPGPU testcases, replace numeric registers in CHECK directives. Using numeric registers is flaky, since as soon as one additional instruction is generated by us, all the tests need to be adapted. llvm-svn: 319544	2017-12-01 14:16:39 +00:00
Siddharth Bhat	43f178bbc9	[PPCGCodeGeneration] Skip arrays with empty extent. Invariant load hoisted scalars, and arrays whose size we can statically compute to be 0 do not need to be allocated as arrays. Invariant load hoisted scalars are sent to the kernel directly as parameters. Earlier, we used to allocate `0` bytes of memory for these because our computation of size from `PPCGCodeGeneration::getArraySize` would result in `0`. Now, since we don't invariant loads as arrays in PPCGCodeGeneration, this problem does not occur anymore. Differential Revision: https://reviews.llvm.org/D35795 llvm-svn: 308971	2017-07-25 12:35:36 +00:00

Author

SHA1

Message

Date

Philip Pfaffe

f6f8b25e58

[NFC] In GPGPU testcases, replace numeric registers in CHECK directives.

Using numeric registers is flaky, since as soon as one additional
instruction is generated by us, all the tests need to be adapted.

llvm-svn: 319544

2017-12-01 14:16:39 +00:00

Siddharth Bhat

43f178bbc9

[PPCGCodeGeneration] Skip arrays with empty extent.

Invariant load hoisted scalars, and arrays whose size we can statically compute
to be 0 do not need to be allocated as arrays.

Invariant load hoisted scalars are sent to the kernel directly as parameters.

Earlier, we used to allocate `0` bytes of memory for these because our
computation of size from `PPCGCodeGeneration::getArraySize` would result in `0`.

Now, since we don't invariant loads as arrays in PPCGCodeGeneration, this
problem does not occur anymore.

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

llvm-svn: 308971

2017-07-25 12:35:36 +00:00

2 Commits