aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/Support/APInt.cpp
diff options
context:
space:
mode:
authorSiddharth Bhat <siddu.druid@gmail.com>2017-05-19 15:07:45 +0000
committerSiddharth Bhat <siddu.druid@gmail.com>2017-05-19 15:07:45 +0000
commitb7f68b8c9e2c499d04a9cc8d8cf4df783ae34bff (patch)
treedee824225e7f63b3efea13b1d36a2fc9d54bbc11 /llvm/lib/Support/APInt.cpp
parentce941c9c380d37a670e3cd3e283ae4070a52859f (diff)
downloadllvm-b7f68b8c9e2c499d04a9cc8d8cf4df783ae34bff.zip
llvm-b7f68b8c9e2c499d04a9cc8d8cf4df783ae34bff.tar.gz
llvm-b7f68b8c9e2c499d04a9cc8d8cf4df783ae34bff.tar.bz2
[Fortran Support] Materialize outermost dimension for Fortran array.
- We use the outermost dimension of arrays since we need this information to generate GPU transfers. - In general, if we do not know the outermost dimension of the array (because the indexing expression is non-affine, for example) then we simply cannot generate transfer code. - However, for Fortran arrays, we can use the Fortran array representation which stores the dimensions of all arrays. - This patch uses the Fortran array representation to generate code that computes the outermost dimension size. Differential Revision: https://reviews.llvm.org/D32967 llvm-svn: 303429
Diffstat (limited to 'llvm/lib/Support/APInt.cpp')
0 files changed, 0 insertions, 0 deletions