This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/25818] Problem with handling optional and entry master arguments
- From: "kargl at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 30 Jul 2006 22:46:56 -0000
- Subject: [Bug fortran/25818] Problem with handling optional and entry master arguments
- References: <bug-25818-87@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #3 from kargl at gcc dot gnu dot org 2006-07-30 22:46 -------
(In reply to comment #2)
> I'm an absolute beginner in programming gfortran, but the following
> patch seems to solve this bug by inserting an if-block into the code
> in order to prevent the access to the NULL pointer in case the array
> is pointing to NULL.
Alexander,
Thanks for the patch, but I think it is only covering up the real
problem. It's more a question of "why is it a NULL pointer?" not
whether we can work around the NULL pointer. I suspect that some
where in resolve.c, gfortran is not properly setting/propagating
information about optional arguments and entry statements.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25818