JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for COMP-FORTRAN-90 Archives


COMP-FORTRAN-90 Archives

COMP-FORTRAN-90 Archives


COMP-FORTRAN-90@JISCMAIL.AC.UK


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

COMP-FORTRAN-90 Home

COMP-FORTRAN-90 Home

COMP-FORTRAN-90  2002

COMP-FORTRAN-90 2002

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: behavior of recursive routines

From:

Tom Clune <[log in to unmask]>

Reply-To:

Fortran 90 List <[log in to unmask]>

Date:

Mon, 21 Oct 2002 08:57:57 -0400

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (106 lines)

Robin Vowels writes:
 > > Date:          Fri, 18 Oct 2002 17:09:46 -0400
 > > From:          Tom Clune <[log in to unmask]>
 > > To:            [log in to unmask]
 >
 > > According to the Fortran standard, how should host-accessible variables
 > > be treated in a recursive routine?  I would have thought that only a single
 > > instance would be created, but due to a bug, I encountered a case where
 > > at least one compiler appears to have created a separate instance at each level.
 >

 > Are you sure?
 > The codes that you give contradict your description.
 > The actual (long) code has "i" defined in the recursive subroutine "SubInit".
 > The wrapping subroutine "ut_tree_iter" not define "i", and your comment
 > says that you accidentally omitted "i" from this routine.

Apologies - my quick stripped down version was not quite complete, and
in my hasty recreation of the problem in the "real" code, I commented
out the wrong declaration of "i".

I include here a full program which demonstrates the problem by
getting different answers on different compilers.  Note that I am now
also making reference to an integer "total" that is also only declared
in main, as a simple mechanism to demonstrate the differing behavior.

!---------------------------------------
Program Main
  Implicit None

  ! These are only declared in main, but used in
  ! the recursive routine sub_init() as well.
  Integer :: i
  Integer :: total

  Integer, Parameter :: N_CHILDREN = 4
  Integer, Parameter :: MAX_DEPTH  = 3

  total = 0
  Call sub_init(1, 0)
  Print*, total

Contains

  Recursive Subroutine sub_init(id, depth)
    Implicit None
    Integer, Intent(In) :: id
    Integer, Intent(In) :: depth

    Integer :: ch_id
    ! Integer "i" is not declared here, but in main instead

    Do i = 1, N_CHILDREN
       If (depth < MAX_DEPTH) Then
          ch_id = N_CHILDREN*id + i
          Call sub_init(ch_id, depth + 1)
          total = total + ch_id
       End If
    End Do

  End Subroutine sub_init

End Program Main
!---------------------------------------

Under absoft:
% ./a.out
   7938

Under Compaq Fortran V5.5-2602
% ./a.out
       12993

Under MIPSpro 7.3.1.1m
% ./a.out
 111

Under Cray CF90 3.5.0.4
# default optimization
% ./a.out
 26
# -O0 optimization gives same as absoft
 7938

From these results I infer that the code is, in fact, not standard
conforming, and I should have declared the integer "i" in routine
sub_init().  In fact, once I have done so, I get the same answer
(7938) under all of the above compilers.  (Well, the default
options for Cray Cf90 still give 26, but I suspect that a compiler
bug is involved here.)  Apparentl, I was just "unfortunate" enough
to be developing under the one compiler that gave the intended
answer even with the illegal code.

Cheers,

- Tom

--

--
Thomas Clune, Ph.D.                   <[log in to unmask]>
Advanced Software Technology Group    Work: 301-286-4635
Science Computing Branch 931          Fax:  301-286-1634
NASA Goddard Space Flight Center
Greenbelt, MD 20771

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

December 2023
February 2023
November 2022
September 2022
February 2022
January 2022
June 2021
November 2020
September 2020
June 2020
May 2020
April 2020
December 2019
October 2019
September 2019
March 2019
February 2019
January 2019
November 2018
October 2018
September 2018
August 2018
July 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
December 2015
November 2015
October 2015
September 2015
August 2015
June 2015
April 2015
March 2015
January 2015
December 2014
November 2014
October 2014
August 2014
July 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
July 2013
June 2013
May 2013
April 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
August 2010
July 2010
June 2010
March 2010
February 2010
January 2010
December 2009
October 2009
August 2009
July 2009
June 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
January 2007
2006
2005
2004
2003
2002
2001
2000
1999
1998
1997


JiscMail is a Jisc service.

View our service policies at https://www.jiscmail.ac.uk/policyandsecurity/ and Jisc's privacy policy at https://www.jisc.ac.uk/website/privacy-notice

For help and support help@jisc.ac.uk

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager