[Bug fortran/33095] MAX with optional arguments gives run-time error

[burnus at gcc dot gnu dot org]

------- Comment #2 from burnus at gcc dot gnu dot org  2007-08-17 13:21 -------
> Oh, sh**, I didn't think about simplification.
> Well, I don't see an easy way to
> have error messages at runtime, so we should simply skip those.

Good idea. As long as the compiler does the right thing (TM) we don't need
run-time errors. Otherwise they make mostly sense with some -f*check-* option.

> PS: I'm not sure it's a 4.3 regression, but it probably is (I can't test right
> now).
I don't think so. The message was introduced with PR31198 and older versions
did probably the same as gfortran 4.2: It crashes if any of the optional
arguments is not present (NULL pointers).


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33095