[Bug fortran/17887] g77 generates code that results in segmentation fault

[Bug fortran/17887] g77 generates code that results in segmentation fault

[macro@linux-mips.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=17887

Maciej W. Rozycki <macro@linux-mips.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |deji_aking at yahoo dot ca

--- Comment #4 from Maciej W. Rozycki <macro@linux-mips.org> ---
*** Bug 37974 has been marked as a duplicate of this bug. ***

[Bug fortran/17887] g77 generates code that results in segmentation fault

[macro@linux-mips.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=17887

Maciej W. Rozycki <macro@linux-mips.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |macro@linux-mips.org

--- Comment #5 from Maciej W. Rozycki <macro@linux-mips.org> ---
*** Bug 95631 has been marked as a duplicate of this bug. ***

[Bug fortran/17887] g77 generates code that results in segmentation fault

[bdavis at gcc dot gnu dot org]

------- Additional Comments From bdavis at gcc dot gnu dot org  2004-10-08 03:15 -------
IMHO, here is the part of the F77 standard that applies:

15.9.3.2 Variables as Dummy Arguments.
A dummy argument that is a variable may be associated with an actual argument
that is a variable, array element, substring, or expression.

If the actual argument is a variable name, array element name, or substring
name, the associated dummy argument may be defined or redefined within the
subprogram. If the actual argument is a constant, a symbolic name of a constant,
a function reference, an expression involving operators, or an expression
enclosed in parentheses, the associated dummy argument must not be redefined
within the subprogram. 


--bud 



-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17887

[Bug fortran/17887] g77 generates code that results in segmentation fault

[bdavis at gcc dot gnu dot org]

------- Additional Comments From bdavis at gcc dot gnu dot org  2004-10-08 03:10 -------
the problem is you are attempting to change the value of a constant.

here is a minimal example:


       CALL FOO(10)
       END
       SUBROUTINE FOO(X)
       INTEGER X
       X=100
       END

gfortran also seg faults with this type of example. i will dig into the standard
and see if this is permitted or not.




--bud davis

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17887

[Bug fortran/17887] g77 generates code that results in segmentation fault

[pinskia at gcc dot gnu dot org]

------- Additional Comments From pinskia at gcc dot gnu dot org  2004-10-08 02:47 -------
The code is invalid, you are passing in a constant to a function and in fortran it is passed by reference 
always.  So you are trying to change the value of -1.0 which is undefined at runtime, in our case both 
g77 and gfortran segfault.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |INVALID


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17887