This is the mail archive of the fortran@gcc.gnu.org mailing list for the GNU Fortran 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] |
Tobias,
I am sorry to be so long in coming back to you - I've been a bit pressed with daytime work.
For the purposes of this patch, the lack of resolution and the impurity indicate that the symbol cannot be a function in a specification expression.Why is that? How does the lack of resolution indicate this? (It could have its PURE attribute set during resolution, couldn't it? Then the code would be legal.)
Not doing this caused regressions with generic interfaces with pure specifics. The symbol points to the generic function, whilst the esym points to the specific. The generic need not (cannot?) be pure.
I'm also interested in these details out of self-interest, My patch for PR 20851 broke resolution of some other permutations of valid objects. This problem is now PR33689.
It looks like you fixed that one:-)
Cheers, - Tobi
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |