On 03/12/2012 01:50 PM, Tobias Burnus wrote:
Additionally, I modified some tree-dump patterns for the extent and
for the base_addr change.
Three more changes: The libgfortran change should have been just a
cleanup, but it seems to also fix a failure. Plus two dump changes. The
number of failu
Dear Tobias,
> At some point, the extent calculation should be updated. Dumps like the
> following hurt, even if -O1 handles* them:
> (((D.1871->dim[0].lower_bound + D.1871->dim[0].extent) + -1) -
> D.1871->dim[0].lower_bound) + 1.
> [* maybe -fstrict-overflow and/or -fno-protect-parens is requir
I have committed a fix for one link issue (spurious
GFC_DESCRIPTOR_STRIDE_BYTES which escaped the renaming to
GFC_DESCRIPTOR_SM) - and changed "data" to "base_addr" for consistency.
Rev. 185216.
Additionally, I modified some tree-dump patterns for the extent and for
the base_addr change.
Re
