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?
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
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
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.
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: jeffrey.armstrong at approximatrix dot com
Target Milestone: ---
Calling a real-valued function without arguments and without providing an
argument list will generate
Assignee: unassigned at gcc dot gnu.org
Reporter: jeffrey.armstrong at approximatrix dot com
Created attachment 33373
-- https://gcc.gnu.org/bugzilla/attachment.cgi?id=33373action=edit
Patch to delete existing .mod file prior to updating
Under Win32 using GNU Fortran 4.9.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62215
--- Comment #2 from Jeffrey Armstrong jeffrey.armstrong at approximatrix dot
com ---
I do not have a copyright assignment on file, but this patch is pretty minor.
I'm willing to fill one out (after I read it, of course), but it shouldn't hold
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62215
--- Comment #5 from Jeffrey Armstrong jeffrey.armstrong at approximatrix dot
com ---
While checking for MinGW (or MinGW-W64) (or non-POSIX Cygwin if it's a
thing...) would allow this to be fixed for Windows, it would continue to assume
that any
