[PATCH] D33688: [Polly] Heap allocation for new arrays

Bonfante Nicolas via Phabricator via llvm-commits llvm-commits at lists.llvm.org
Tue Jun 6 14:43:25 PDT 2017


niosega added a comment.

In https://reviews.llvm.org/D33688#774231, @Meinersbur wrote:

> I am wondering why you decided for a global stack-or-heap property. I'd assumed that this is a per-array decision. For instance, Roman's gemm optimization is designed to fit on the stack, there is no reason to allocate it on the heap.


The global stack-or-heap property is just for debugging purpose (as explained in the summary). I publish my code in phabricator so that I can have feedback on the malloc creation. I am working in parallel on adding the possibility to specify in the json file if we want heap or stack array, as Andreas described in an inline comment.


https://reviews.llvm.org/D33688





More information about the llvm-commits mailing list