This is the mail archive of the fortran@gcc.gnu.org mailing list for the GNU Fortran project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
On 04/03/11 17:03, Tobias Burnus wrote:For the support, the scalarizer had to be modified and the cobounds had to be saved in the descriptor (and in TYPE_LANG_SPECIFIC(node)).
I'm all but an expert on this area (maybe you could ask Mikael for his opinion on the scalarizer changes),
but isn't this TYPE_LANG_SPECIFIC stuff only for compile-time known things?
@@ -4129,7 +4129,12 @@ gfc_is_coindexed (gfc_expr *e)
It seems to me there's some tab-vs-space issue here (for the int and for lines).
@@ -3152,6 +3173,14 @@ gfc_conv_ss_startstride (gfc_loopinfo * loop)
That doesn't change anything, but I'd rather have a "break" for the new cases (even though there was none before and fall-through just has the same effect). It seems clearer to me as you don't do anything "special" via fall-through.
@@ -3739,7 +3780,7 @@ gfc_conv_loop_setup (gfc_loopinfo * loop, locus * where)
+ if (loopspec[n] != NULL /*|| n >= loop->dimen*/)
Or rather remove it and add later seems also like a good possibility to me.
@@ -7386,8 +7484,9 @@ gfc_walk_variable_expr (gfc_ss * ss, gfc_expr * expr)
+ newss->data.info.dim[newss->data.info.dimen+newss->data.info.codimen] = n;
Nit: Please add appropriate spacing around the "+" in the "long line". (As it is in the hunk above.)
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |