https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85575
kargl at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |kargl at gcc dot gnu.org
--- Comment #2 from kargl at gcc dot gnu.org ---
(In reply to Jürgen Reuter from comment #1)
> Ok, after discussion on the Intel Forum I found out that this is based on
> Section 7.1.11p7 of the f2008 standard , Specification expression:
>
> A variable in a specication expression shall have its type and type
> parameters, if any, specified by a previous
> declaration in the same scoping unit, by the implicit typing rules in
> effect for the scoping unit, or by host or use
> association. If a variable in a specification expression is typed by the
> implicit typing rules, its appearance in any
> subsequent type declaration statement shall confirm the implied type and
> type parameters.
>
> But it is not clear whether the compiler actually has to detect this.
If it is a numbered constraint, then the compiler must detect the problem.
If it is unnumbered, then the above "shall"'s apply to the program(mer).
A compiler can, but is not required to report a problem.
