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  2000

COMP-FORTRAN-90 2000

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: Re: Bug or Feature?

From:

Van Snyder <[log in to unmask]>

Reply-To:

Van Snyder <[log in to unmask]>

Date:

Wed, 07 Jun 2000 12:07:44 -0700

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (60 lines)


You may remember that I tried to get a pointer to a piece of an array,
but reshaped with a different rank, by passing the array through a
function that returned a pointer to its argument.  Kurt has pointed out
why this shouldn't be expected to work.  The reason is the same as the
reason my initial attempt at getting this functionality didn't work: The
TARGET attribute doesn't "leak through" the RESHAPE intrinsic function
from its SOURCE argument to its result.

What I originally tried was something like

  P2 => reshape ( T1, (/4,4/) )

There are times when one wants to view a piece of a vector as an array
having rank higher than one, and vice versa.  In our application, the
vector is a "state vector" for a nonlinear least-squares problem, and
the multidimensional array views of pieces of it correspond to the
physical properties/coordinates of the data -- pressure, frequency,
chemical composition, longitude, latitude....  The vector view is used
(required!) by (large) previously-written procedures to solve nonlinear
least-squares problems, and the array view is used (required!) by
(large) previously-written procedures to evaluate a function having
(nonlinear) parameters for which we're trying to solve.  Taking a copy
is undesirable, because the state vector has about 10^6 elements.

One could, of course, write a function that takes our coordinates and
produces a 1-D index, according to Fortran's rules for array element
order, but (1) that is a bit of work (that the compiler already knows how
to do), and (2) it can't take section arguments or produce a section.

It would make RESHAPE unique among intrinsic functions to specify that
its result has the TARGET attribute if and only if its first argument
does, but that's what would be useful in our case.  Changing RESHAPE in
this way would not invalidate any existing program.  There are other
intrinsic functions that are somewhat "irregular" from the point of
view of non-intrinsic functions -- MAX comes immediately to mind -- so
there would be some precedent to having yet another unusual one.

How do J3, WG5 and vendors feel about adding something like "It has the
TARGET attribute if and only if SOURCE has the TARGET attribute, SOURCE
is a rank-one array that is not an array section with a vector subscript,
and the PAD and ORDER arguments are absent" at the end of the "Result
Characteristics" paragraph in the definition of RESHAPE (13.14.90 in
the Fortran 95 standard)?  The restrictions are intended to allow RESHAPE
to return SOURCE, not a copy of it.  Maybe more restrictions are necessary,
or all of the above aren't, but you get the idea.  The "rank-one" part
could be relaxed, but under difficult-to-describe conditions --
essentially that the elements of SOURCE have uniform spacing in memory.
I think it's difficult to specify this so it can be verified statically.
Consider the cases when SOURCE is a pointer, or a dummy argument with
assumed shape.

Best regards,
Van Snyder




%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

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