https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79612
--- Comment #4 from Dominique d'Humieres <dominiq at lps dot ens.fr> --- > I cannot think of this happening with normal code. An > internal error might be better, but internal_error does not > take printf-style arguments. This code has been introduced at revision r149792 (Jul 19 2009). AFAIU the above comment, the error can only trigger if the user code is miscompiled. Is this correct? If yes, should this error be suppressed or at least the message changed to something such as "Bad code: incorrect rank of return array in %s intrinsic is %ld, should be 1. Please report"? Note a duplicated 'must' in the comment /* Bounds checking for the return values of the iforeach functions (such as maxloc and minloc). The extent of ret_array must must match the rank of array. */
