On 04/11/2011 06:04 PM, Michael Matz wrote:
===================================================================
*** trans-array.c (revision 172206)
--- trans-array.c (working copy)
*************** gfc_trans_auto_array_allocation (tree de
[...]
! gfc_add_init_cleanup (block, inittree, tmp);
}
I get the fatal warning:
.../gcc/fortran/trans-array.c: In function
‘gfc_trans_auto_array_allocation’:
..../gcc/fortran/trans-array.c:4881:24: error: ‘tmp’ may be used
uninitialized in this function [-Werror=uninitialized]
which is the line quoted above.
* * *
Regarding the goal of the patch: I like the idea and I think it is
rather useful. It is unfortunate that running out of stack space causes
segfaults, which is not very user friendly, but I think HPC users - and
in particular Intel compiler users - are used to have "ulimit -s
unlimited" (or some large value), which also HPC admins set. For
instance, on the login node of our HPC cluster (2*quadcore/node; 24 GB
RAM/node, 2200 nodes) one has 3 GB stack space by default (soft and hard
limit) - I think the value on the compute nodes is the same.
Tobias
