This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/47745] [OOP] Segfault with CLASS(*) and derived type dummy arguments
- From: "kargl at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Thu, 17 Feb 2011 02:57:30 +0000
- Subject: [Bug fortran/47745] [OOP] Segfault with CLASS(*) and derived type dummy arguments
- Auto-submitted: auto-generated
- References: <bug-47745-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47745
--- Comment #11 from kargl at gcc dot gnu.org 2011-02-17 02:57:08 UTC ---
(In reply to comment #10)
>
> I'm learning Fortran 03 and 08 at the moment, so I'm likely to compile
> a lot of invalid code. Should I report a bug every time gfortran
> accepts code it should reject, or try to pick the serious ones?
Yes, report bugs. This includes gfortran accepting
invalid code, crashing on valid code, crashing on
invalid code. Bugs, that go unreported, can't be
fixed.