------- Additional Comments From kargl at gcc dot gnu dot org 2005-08-24 17:54 ------- Changing the * in the format statements and the encode/decode statements may help prevent gfortran from getting stuck, but there are several other nonstandard statements in the code.
To deal with gfortran getting stuck, I think the simplest solution is to introduce a -ferror-count=N option where gfortran will die with a fatal error after N error messages have been emitted. This, of course, only papers over the problem, but redesigning gfortran's error handling/reporting is going to be a really big effort. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23538
