From patchwork Sat Sep 4 14:24:03 2010 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: [fortran,4/11] Inline transpose part 1 X-Patchwork-Submitter: Mikael Morin X-Patchwork-Id: 63783 Message-Id: <4C825683.80801@sfr.fr> To: "fortran@gcc.gnu.org" , gcc-patches Date: Sat, 04 Sep 2010 16:24:03 +0200 From: Mikael Morin List-Id: The innermost stride of a full array is not necessarily stride[0] if we are accessing it transposed. OK for trunk? 2010-09-03 Mikael Morin * trans-array.c (gfc_trans_preloop_setup): Unconditionally use the dim array to get the stride in the innermost loop. diff --git a/trans-array.c b/trans-array.c index 5086641..d4a0542 100644 --- a/trans-array.c +++ b/trans-array.c @@ -2733,12 +2733,13 @@ gfc_trans_preloop_setup (gfc_loopinfo * loop, int dim, int flag, info->offset, index); info->offset = gfc_evaluate_now (info->offset, pblock); } - - i = loop->order[0]; - stride = gfc_conv_array_stride (info->descriptor, info->dim[i]); } - else - stride = gfc_conv_array_stride (info->descriptor, 0); + + i = loop->order[0]; + /* For the time being, the innermost loop is unconditionally on + the first dimension of the scalarization loop. */ + gcc_assert (i == 0); + stride = gfc_conv_array_stride (info->descriptor, info->dim[i]); /* Calculate the stride of the innermost loop. Hopefully this will allow the backend optimizers to do their stuff more effectively.