[Bug fortran/104812] Construct-name with same variable name in scope

2022-04-05 Thread fruitclover at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104812 --- Comment #6 from Mike K. --- Thanks a lot for the guidance, posted patch.

[Bug fortran/104812] Construct-name with same variable name in scope

2022-04-05 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104812 kargl at gcc dot gnu.org changed: What|Removed |Added Resolution|INVALID |--- Ever confirmed|0

[Bug fortran/104812] Construct-name with same variable name in scope

2022-04-05 Thread fruitclover at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104812 --- Comment #4 from Mike K. --- Created attachment 52749 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52749=edit propose to return an error if constuct-name clashes with variable name > Note, the prohibition in the standard is not a

[Bug fortran/104812] Construct-name with same variable name in scope

2022-03-10 Thread sgk at troutmask dot apl.washington.edu via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104812 --- Comment #3 from Steve Kargl --- On Thu, Mar 10, 2022 at 11:27:41AM +, fruitclover at gmail dot com wrote: > > --- Comment #2 from Mike K. --- > Thanks, and subroutine s2 conforming Fortran 2018, 19.4, right? > No. The logical

[Bug fortran/104812] Construct-name with same variable name in scope

2022-03-10 Thread fruitclover at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104812 --- Comment #2 from Mike K. --- Thanks, and subroutine s2 conforming Fortran 2018, 19.4, right?

[Bug fortran/104812] Construct-name with same variable name in scope

2022-03-07 Thread kargl at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104812 kargl at gcc dot gnu.org changed: What|Removed |Added CC||kargl at gcc dot gnu.org