The current code has redundancy with the infrastructure for
declaration checking that can be replaced by better usage of
the parse tree walking framework. This also fixes LLVM flang
bug #58971.
Details
Details
Diff Detail
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
Comment Actions
Aside fromt the question, all builds and tests correctly and looks good.
flang/test/Semantics/resolve61.f90 | ||
---|---|---|
73 | This error used to have a more accurate message. Now we seem to be treating the appearance of t in a pointer statement as a redeclaration. This seems OK to me, but I just wanted to make sure that this is what you intended. |
flang/test/Semantics/resolve61.f90 | ||
---|---|---|
73 | It's good, and it's the right message for situations where a name gets declared more than once in a scope and is not one of the two cases where Fortran allows it. |
This error used to have a more accurate message. Now we seem to be treating the appearance of t in a pointer statement as a redeclaration. This seems OK to me, but I just wanted to make sure that this is what you intended.