[Bug fortran/95038] Not treating function result name as a variable.

2022-06-10 Thread longb at cray dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95038 --- Comment #10 from Bill Long --- The original issue seems fixed in 12.1. However, the wording of the ERROR message (objecting that something is not a DATA entity when it really is) could still be improved. Can we either convert this bug to th

[Bug fortran/95038] Not treating function result name as a variable.

2021-02-01 Thread longb at cray dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95038 --- Comment #9 from Bill Long --- The original test is not conforming due to the missing IMPORT statement. However, the error message , which I assume is for the second non-blank line in the listing, seems odd. The standard says "If RESULT do

[Bug fortran/95038] Not treating function result name as a variable.

2021-02-01 Thread drikosev at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95038 Ev Drikos changed: What|Removed |Added CC||drikosev at gmail dot com --- Comment #8 fro

[Bug fortran/95038] Not treating function result name as a variable.

2021-01-29 Thread burnus at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95038 Tobias Burnus changed: What|Removed |Added CC||burnus at gcc dot gnu.org --- Comment #7

[Bug fortran/95038] Not treating function result name as a variable.

2021-01-26 Thread longb at cray dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95038 --- Comment #6 from Bill Long --- Is there a released version with the fix noted in this bug?

[Bug fortran/95038] Not treating function result name as a variable.

2020-11-23 Thread longb at cray dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95038 --- Comment #5 from Bill Long --- Original submitter asking for a fixed-in version number.

[Bug fortran/95038] Not treating function result name as a variable.

2020-10-18 Thread longb at cray dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95038 --- Comment #4 from Bill Long --- Original submitter is looking for a fix version for this issue. Any predictions?

[Bug fortran/95038] Not treating function result name as a variable.

2020-07-07 Thread arjen.markus895 at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95038 Arjen Markus changed: What|Removed |Added CC||arjen.markus895 at gmail dot com --- Com

[Bug fortran/95038] Not treating function result name as a variable.

2020-05-10 Thread kargl at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95038 kargl at gcc dot gnu.org changed: What|Removed |Added Ever confirmed|0 |1 CC|

[Bug fortran/95038] Not treating function result name as a variable.

2020-05-10 Thread longb at cray dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95038 --- Comment #1 from Bill Long --- Note that for the greatly simplified test case > cat test3.f90 real(4) function x (a) real(kind(x)) a(:) print *, kind(x) end function x gfortran compiles with no error. So maybe th