forked from OSchip/llvm-project
02f3fec391
This change makes sure that we compute the element size and the byte stride based on the target representation of the element type. For example, when REAL*10 is mapped to x86_fp80 each element occupies 16 bytes rather than 10 because of the padding. Note that the size computation method used here actually returns the distance between two adjacent element of the *same* type in memory (which is equivalent to llvm::DataLayout::getTypeAllocSize()). It does not return the number of bytes that may be overwritten by storing a value of the specified type (e.g. what can be computed via llvm::DataLayout::getTypeStoreSize(), but not available in mlir::DataLayout). Differential Revision: https://reviews.llvm.org/D133508 |
||
---|---|---|
.. | ||
array-constructor.f90 | ||
array-pointer.f90 | ||
array-subscripts.f90 | ||
character-1.f90 | ||
degenerate.f90 | ||
forall-2.f90 | ||
forall-allocatable-2.f90 | ||
forall-allocatable.f90 | ||
forall-array.f90 | ||
forall-construct-2.f90 | ||
forall-construct-3.f90 | ||
forall-construct-4.f90 | ||
forall-construct.f90 | ||
forall-ranked.f90 | ||
forall-slice.f90 | ||
forall-stmt.f90 | ||
forall-where-2.f90 | ||
forall-where.f90 | ||
scalar-substring.f90 | ||
test9.f90 |