This is the mail archive of the
fortran@gcc.gnu.org
mailing list for the GNU Fortran project.
Re: The root cause for SEGV in evaluating fortran function call, any solution or suggestion?
- From: Daniel Jacobowitz <drow at false dot org>
- To: Jim Blandy <jimb at redhat dot com>
- Cc: Mark Kettenis <mark dot kettenis at xs4all dot nl>, woodzltc at cn dot ibm dot com,gdb at sources dot redhat dot com, fortran at gcc dot gnu dot org
- Date: Sun, 6 Nov 2005 19:02:29 -0500
- Subject: Re: The root cause for SEGV in evaluating fortran function call, any solution or suggestion?
- References: <Pine.LNX.4.63.0508221743470.10411@linux.site> <Pine.LNX.4.63.0511021033530.3549@linux.site> <200511021551.jA2FpO7D009728@elgar.sibelius.xs4all.nl> <vt2oe52npn7.fsf@theseus.home.>
On Wed, Nov 02, 2005 at 11:42:36PM -0800, Jim Blandy wrote:
> The types in the debug information should not reflect the extra level
> of indirection; the fact that they're passed by reference is just part
> of the meaning of a Fortran function call. But the location
> expression should encode the extra level of indirection.
This seems perfectly sensible to me. But the example Wu posted earlier
does not agree: today gfortran apparently puts out the indirections
explicitly.
Paul Brook had this to say when I asked him:
When a user says "p foo" they should get the value, not the address of
the argument.
So it sounds like gfortran will need to be fixed.
--
Daniel Jacobowitz
CodeSourcery, LLC