https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80610
Jerry DeLisle <jvdelisle at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jvdelisle at gcc dot gnu.org
--- Comment #12 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> ---
I am going to have to beg to differ here with everyone. First gfortran/gcc is
not crap. Throwing insults back and forth is useless. It is an extremely
valuable tool for an extremely low cost, as in free. No one has a right to
complain.
With that said. I do think there is a serious implementation issue. I decided
to actually try the code provided and it crapped my machine and required power
down and restart. That is ridiculous.
A better implementation would be that either set a reasonable limit for hard
coded initialization of large arrays and issue a diagnostic if that is
exceeded. That would be easy to do. Or, better yet, don't expand/initialize the
array at compile time. We should set some sort of global constructor/iterator
that gets finally executed at run time, but at compile time, we know the value
of any aspect of the array as a parameter with out actually needing to expand
it.
Yes that will take some frontend magic and we have so few people to support
gfortran (for free remember) that we may not be able to get to it.
I don't think the report is invalid at all.
