[Bug fortran/18578] intent(inout) 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-30 05:45 --- Subject: Bug 18578 Author: pault Date: Mon Jan 30 05:45:06 2006 New Revision: 110394 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=110394 Log: 2006-01-30 Paul Thomas <[EMAIL PROTECTED]> PR fortran/

[Bug fortran/18578] intent(inout) violation is not detected

2006-01-29 Thread pault at gcc dot gnu dot org
--- Comment #3 from pault at gcc dot gnu dot org 2006-01-29 16:31 --- Subject: Bug 18578 Author: pault Date: Sun Jan 29 16:31:24 2006 New Revision: 110376 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=110376 Log: 2006-01-29 Paul Thomas <[EMAIL PROTECTED]> PR fortran/

[Bug fortran/18578] intent(inout) violation is not detected

2005-12-31 Thread pinskia at gcc dot gnu dot org
--- Comment #2 from pinskia at gcc dot gnu dot org 2006-01-01 05:58 --- Yes this is a dup of bug 20857. *** This bug has been marked as a duplicate of 20857 *** -- pinskia at gcc dot gnu dot org changed: What|Removed |Added ---

[Bug fortran/18578] intent(inout) 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:46 --- I assume you are talking about: call foo(3.0) if so confirmed, there should be a warning about this being undefined. -- What|Removed |Added