This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
This cannot easily be implemented. However, this paragraph does imply that a reference to the variable, in whose declaration the specification expressions appear, should be preceeded by the appearance of the requisite variables as dummy argments. Furthermore, it follows that if any one of the variables appear, they all must. This is what I have implemented.[...]
The second part of the patch ensures that if one variable from a specification expression appears as a parameter of an entry, then all the variables in that expression must be parameters of the entry. This is done by resolve_index_entries, which is called during symbol resolution. It uses existing calls to gfc_resolve_expr to collect the variables used in the specification expression. Using this list, the new function checks the variables against each of the entry formal argument lists.
subroutine foo(a,b,c) integer a, b integer c(a+b) ... entry bar(b) ... end subroutine
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |