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  March 2015

COMP-FORTRAN-90 March 2015

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: Finalization of arrays when type finalizer is recursive

From:

Malcolm Cohen <[log in to unmask]>

Reply-To:

Fortran 90 List <[log in to unmask]>

Date:

Tue, 17 Mar 2015 09:04:26 +0900

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (66 lines)

Hi,

<<<
"First, elemental implies pure -- elemental is all you need" - no, not with 
Fortran 2008.
>>>

As Neil commented, Fortran 2008 has not changed the meaning of the ELEMENTAL 
keyword, so a Fortran 95/2003 program using ELEMENTAL has identical semantics, 
i.e. in the absence of IMPURE, ELEMENTAL=>PURE.

<<<
So how does NAg compiler in terms of -C=recursion (or -C=all)?  Is that on by 
default?
>>>

No.

<<<
  And is there a way to turn it off?
>>>

The -C=recursion option turns it on.  Omitting the option leaves it off.

<<<
  And when the check of "invalid recursion" (via -C=all or -C=recursion) is 
applied, is it checking against the current Fortran standard (which simply has 
an artificial constraint)
>>>

It is NOT an artificial constraint!

<<<
or a true systems problem where recursion can lead to stack corruption, etc.
>>>

A procedure that is compiled as being "non-recursive" can do static allocation 
of (non-automatic) local unSAVEd variables.  Obviously that is going to silently 
return the wrong answer if it gets called recursively.  Thus there is a good 
reason for the existence of the RECURSIVE keyword in the standard and 
the -C=recursive option for the NAG compiler.

Fortran 2015 still permits non-recursive procedures, the change is that "by 
default" every procedure is recursive.  You can declare a procedure to be 
non-recursive using the (new) NON_RECURSIVE keyword.

>should cause no other true application issues at the assembly level - no stack 
>corruption, no memory leaks,

With current hardware it is not stack corruption that is likely to be the 
problem, it is the possibility of silent wrong answers.

>I have tested it extensively with Intel compiler.

It might well be that the Intel compiler has put some or all of your local 
variables onto the stack (instead of statically allocating); different compilers 
are known to use different heuristics for this, and the heuristics are known to 
be affected by other compiler options.  Or it might be that your tests failed to 
detect this.  Whatever, assuming the compiler will always use stack allocation 
in a non-RECURSIVE procedure for unSAVEd variables is a pretty risky assumption, 
and one that I do not recommend.

Cheers,
-- 
................................Malcolm Cohen, Nihon NAG, Tokyo. 

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