[Bug fortran/80467] Function Without Arguments Fails to Generate Error When Declared Later

2019-04-22 Thread dominiq at lps dot ens.fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80467 Dominique d'Humieres changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug fortran/80467] Function Without Arguments Fails to Generate Error When Declared Later

2019-04-22 Thread dominiq at lps dot ens.fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80467 Dominique d'Humieres changed: What|Removed |Added CC||g.granda at irya dot unam.mx ---

[Bug fortran/80467] Function Without Arguments Fails to Generate Error When Declared Later

2018-11-27 Thread gs...@t-online.de
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80467 G. Steinmetz changed: What|Removed |Added CC||gs...@t-online.de --- Comment #8 from G.

[Bug fortran/80467] Function Without Arguments Fails to Generate Error When Declared Later

2017-08-17 Thread jeffrey.armstrong at approximatrix dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80467 --- Comment #7 from Jeffrey Armstrong --- Any update on this Internal Compiler Error? Has anyone looked into it further?

[Bug fortran/80467] Function Without Arguments Fails to Generate Error When Declared Later

2017-05-03 Thread anlauf at gmx dot de
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80467 --- Comment #6 from Harald Anlauf --- The code is properly rejected e.g. by the Intel compiler: pr80467.f90(16): error #6423: This name has already been used as an external function name. [GETVALUE] compareTo = GetValue --

[Bug fortran/80467] Function Without Arguments Fails to Generate Error When Declared Later

2017-05-02 Thread jeffrey.armstrong at approximatrix dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80467 --- Comment #5 from Jeffrey Armstrong --- It's actually easy to trigger the ICE with a small change. The following causes an internal compiler error wiht GCC 6.3 under MinGW-W64: ! program noargs

[Bug fortran/80467] Function Without Arguments Fails to Generate Error When Declared Later

2017-05-02 Thread jeffrey.armstrong at approximatrix dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80467 --- Comment #4 from Jeffrey Armstrong --- > AFAICT you get the internal error only with compilers configured with > --enable-checking=yes. I was refering to a compiler crash occurring on a non-trivial program: internal compiler error: in conve

[Bug fortran/80467] Function Without Arguments Fails to Generate Error When Declared Later

2017-05-02 Thread dominiq at lps dot ens.fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80467 --- Comment #3 from Dominique d'Humieres --- > I agree that the code is invalid, and it is the user's responsibility. > However, I don't think an internal compiler error is appropriate in this > case. AFAICT you get the internal error only wi

[Bug fortran/80467] Function Without Arguments Fails to Generate Error When Declared Later

2017-05-02 Thread jeffrey.armstrong at approximatrix dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80467 --- Comment #2 from Jeffrey Armstrong --- I agree that the code is invalid, and it is the user's responsibility. However, I don't think an internal compiler error is appropriate in this case. An actual error would be preferable.

[Bug fortran/80467] Function Without Arguments Fails to Generate Error When Declared Later

2017-05-01 Thread dominiq at lps dot ens.fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80467 Dominique d'Humieres changed: What|Removed |Added Priority|P3 |P5 Status|UNCONFIRMED