Re: The root cause for SEGV in evaluating fortran function call, any solution or suggestion?

[Wu Zhou <woodzltc@cn.ibm.com>]

On Mon, 7 Nov 2005, Daniel Jacobowitz wrote:

> On Mon, Nov 07, 2005 at 12:51:59PM +0800, Wu Zhou wrote:
> > You are quite right.  Following your pointer, I made another patch and it 
> > now passed with both g77 (3.4.4) and gfortran (4.0.1) on a x86 box.  I 
> > didn't consider the red zone in AMD64 architecture, so maybe it won't work 
> > on it.  I will try to find a chance to test it on other platform, such as 
> > ppc64 or any other platform I can get access to.
> > 
> > Appended is the patch.  Any comments and suggestion are highly 
> > appreciated!
> 
> Just to be clear: the patch is _not_ acceptable as is.  We need to
> decide what gfortran's debugging information should look like, and how
> the transformation should be controlled by language.  Casting an
> integer to a pointer by pushing it to the stack this way is not the
> correct behavior for any other language.

That is okay.  I am very happy to know how gfortran should handle this 
kind of case.  Will you talk with gfortran guys on this?  If possible, 
would you please include me in the cc-list of your correspondence?  That 
will be highly appreciated.
 
Regards
- Wu Zhou