Re: Syntax check for IMPLICIT statement

From: "Michael Metcalf" <michaelmetcalf@xxxxxxxxxxxxxx>
Date: Sun, 27 Apr 2008 23:42:29 GMT

"James Van Buskirk" <not_valid@xxxxxxxxxxx> wrote in message
news:wpmdnYLdJ7wLl4jVnZ2dnUVZ_jednZ2d@xxxxxxxxxxxxxx

In attempting to create a digestible version of a program that gives
gfortran an ICE and causes incorrect output for ifort, the critical
factor for both seems to be a line such as:

implicit character(len=*,kind=kind('A')) (Q)

"For a scalar named constant or for a dummy argument ... a len-value may be
specified as an asterisk" ("Fortran 95/2003 Explained", Section 7.13).

HTH,

Mike Metcalf

.

Follow-Ups:
- Re: Syntax check for IMPLICIT statement
  - From: glen herrmannsfeldt

References:
- Syntax check for IMPLICIT statement
  - From: James Van Buskirk

Prev by Date: Syntax check for IMPLICIT statement
Next by Date: Re: Syntax check for IMPLICIT statement
Previous by thread: Syntax check for IMPLICIT statement
Next by thread: Re: Syntax check for IMPLICIT statement
Index(es):
- Date
- Thread

Relevant Pages

LEN of subroutine variables
... implicit none ... When this code is compiled with gfortran or ifort, ... valgrind complains about "Conditional jump or ...
(comp.lang.fortran)
glibc detected *** ./run.out: munmap_chunk(): invalid pointer:
... implicit none ... the code is working fine with ifort but fails on other compiler. ...
(comp.lang.fortran)
Re: Syntax check for IMPLICIT statement
... -|gfortran an ICE and causes incorrect output for ifort, ... -|In the sense that if the LEN is changed to 3 both ifort and gfortran ...
(comp.lang.fortran)
Re: Syntax check for IMPLICIT statement
... gfortran an ICE and causes incorrect output for ifort, ...
(comp.lang.fortran)
Re: Syntax check for IMPLICIT statement
... gfortran an ICE and causes incorrect output for ifort, ...
(comp.lang.fortran)