[Bug fortran/18579] intent(out) violation is not detected

2006-01-30 Thread pinskia at gcc dot gnu dot org 


-- 

pinskia at gcc dot gnu dot org changed:

   What|Removed |Added

   Target Milestone|--- |4.1.0


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

[Bug fortran/18579] intent(out) violation is not detected

2006-01-29 Thread pault at gcc dot gnu dot org 


--- Comment #4 from pault at gcc dot gnu dot org  2006-01-29 16:31 ---
Subject: Bug 18579

Author: pault
Date: Sun Jan 29 16:31:24 2006
New Revision: 110376

URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=110376
Log:
2006-01-29  Paul Thomas  [EMAIL PROTECTED]

PR fortran/18578
PR fortran/18579
PR fortran/20857
PR fortran/20885
* interface.c (compare_actual_formal): Error for INTENT(OUT or INOUT)
if actual argument is not a variable.

2006-01-29  Paul Thomas  [EMAIL PROTECTED]

PR fortran/18578
PR fortran/18579
PR fortran/20857
PR fortran/20885
* gfortran.dg/intent_out_1.f90: New test.

Added:
trunk/gcc/testsuite/gfortran.dg/intent_out_1.f90
Modified:
trunk/gcc/fortran/ChangeLog
trunk/gcc/fortran/interface.c
trunk/gcc/testsuite/ChangeLog


-- 


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

[Bug fortran/18579] intent(out) violation is not detected

2006-01-29 Thread pault at gcc dot gnu dot org 


--- Comment #5 from pault at gcc dot gnu dot org  2006-01-30 05:45 ---
Subject: Bug 18579

Author: pault
Date: Mon Jan 30 05:45:06 2006
New Revision: 110394

URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=110394
Log:
2006-01-30  Paul Thomas  [EMAIL PROTECTED]

PR fortran/18578
PR fortran/18579
PR fortran/20857
PR fortran/20885
* interface.c (compare_actual_formal): Error for INTENT(OUT or INOUT)
if actual argument is not a variable.

PR fortran/17911
* expr.c (gfc_check_assign, gfc_check_pointer_assign): Emit error if
the lvalue is a use associated procedure.

PR fortran/20895
PR fortran/25030
* expr.c (gfc_check_pointer_assign): Emit error if lvalue and rvalue
character lengths are not the same.  Use gfc_dep_compare_expr for the
comparison.
* gfortran.h: Add prototype for gfc_dep_compare_expr.
* dependency.h: Remove prototype for gfc_dep_compare_expr.

2006-01-30  Paul Thomas  [EMAIL PROTECTED]

PR fortran/18578
PR fortran/18579
PR fortran/20857
PR fortran/20885
* gfortran.dg/intent_out_1.f90: New test.

PR fortran/17911
* gfortran.dg/procedure_lvalue.f90: New test.

PR fortran/20895
PR fortran/25030
* gfortran.dg/char_pointer_assign_2.f90: New test.
* gfortran.dg/char_result_1.f90: Correct unequal charlen pointer
assignment to be consistent with standard.
* gfortran.dg/char_result_2.f90: The same.
* gfortran.dg/char_result_8.f90: The same.

Added:
branches/gcc-4_1-branch/gcc/testsuite/gfortran.dg/char_pointer_assign_2.f90
branches/gcc-4_1-branch/gcc/testsuite/gfortran.dg/intent_out_1.f90
branches/gcc-4_1-branch/gcc/testsuite/gfortran.dg/procedure_lvalue.f90
Modified:
branches/gcc-4_1-branch/gcc/fortran/ChangeLog
branches/gcc-4_1-branch/gcc/fortran/dependency.h
branches/gcc-4_1-branch/gcc/fortran/expr.c
branches/gcc-4_1-branch/gcc/fortran/gfortran.h
branches/gcc-4_1-branch/gcc/fortran/interface.c
branches/gcc-4_1-branch/gcc/testsuite/ChangeLog
branches/gcc-4_1-branch/gcc/testsuite/gfortran.dg/char_result_1.f90
branches/gcc-4_1-branch/gcc/testsuite/gfortran.dg/char_result_2.f90
branches/gcc-4_1-branch/gcc/testsuite/gfortran.dg/char_result_8.f90


-- 


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

[Bug fortran/18579] intent(out) violation is not detected

2006-01-29 Thread pault at gcc dot gnu dot org 


--- Comment #6 from pault at gcc dot gnu dot org  2006-01-30 05:47 ---
Fixed on trunk and 4.1.

Paul


-- 

pault at gcc dot gnu dot org changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution||FIXED


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

[Bug fortran/18579] intent(out) violation is not detected

2005-12-15 Thread paul dot richard dot thomas at cea dot fr 


--- Comment #2 from paul dot richard dot thomas at cea dot fr  2005-12-15 
09:17 ---
The test case is OK;  the variable b is definable, so can be used as an actual
argument for a dummy with intent OUT/INOUT.  DF6.0 and Lahey agree with me on
this.

Gfortran does the right thing if the intent is changed to IN.  However, if the
testcase is modified to

call foo (b + 3.0)

it still does not give an error and that is a bug because the expression is not
definable.

I will produce a patch for it.


-- 

paul dot richard dot thomas at cea dot fr changed:

   What|Removed |Added

 CC||paulthomas2 at wanadoo dot
   ||fr


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

[Bug fortran/18579] intent(out) violation is not detected

2005-12-15 Thread paul dot richard dot thomas at cea dot fr 


--- Comment #3 from paul dot richard dot thomas at cea dot fr  2005-12-15 
14:10 ---

Sorry, I goofed; the testcase is not OK - you are right on the righthand side,
so to speak.

Paul


-- 


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

[Bug fortran/18579] intent(out) violation is not detected

2004-11-20 Thread pinskia at gcc dot gnu dot org 

--- Additional Comments From pinskia at gcc dot gnu dot org  2004-11-20 
17:48 ---
Confirmed.

-- 
   What|Removed |Added

   Severity|normal  |minor
 Status|UNCONFIRMED |NEW
 Ever Confirmed||1
   Keywords||diagnostic
   Last reconfirmed|-00-00 00:00:00 |2004-11-20 17:48:45
   date||


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