------- Comment #4 from burnus at gcc dot gnu dot org 2009-05-26 19:29 -------
s/main_program/is_main_program/
CLOSE as WONTFIX. As Andrew pointed out, there are a couple of issues using
static memory:
1. The middle end does not optimize static variables that well as it does not
know about non-recursive procedures
2. Marking loop variables etc. as static does not work well in the context of
OpenMP's private. This problem can be reduced by using a certain threshold (as
currently done for local variables), but it always exists
3. Given all the trouble, it is unlikely that a real-world program only has a
too large array in the main program (which can be cured by this patch); more
likely is that further large arrays exists in subroutines etc. For those this
patch won't help, but "ulimit -s unlimited" does.
4. This seems to be a relatively rarely reported problem; general stack limit
problems are more common, though.
-> CLOSE
--
burnus at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |WONTFIX
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34053
