https://www.jiscmail.ac.uk/cgi-bin/webadmin?RSS&L=COMP-FORTRAN-90&v=1.0COMP-FORTRAN-90 List
https://www.jiscmail.ac.uk/cgi-bin/webadmin?A0=COMP-FORTRAN-90
COMP-FORTRAN-90 List Archives2015-01-21T19:20:50ZPowered by L-Soft's LISTSERV mailing list manager
http://www.lsoft.com/products/listserv-powered.asp
http://www.lsoft.com/images/listserv_small.gifRe: fortran sum intrinsic question
https://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;f080bd8a.1501
On 1/21/2015 2:10 PM, Tobias Burnus wrote:<br>> Ian D Chivers wrote:<br>>> Jane and I are writing some new examples<br>>> for the next edition of the book<br>>> and have been benchmarking an openmp<br>>> summation example and comparing the timing<br>>> against the sum intrinsic.<br>>><br>>> are we likely to see parallel<br>>> versions of any of the intrinsics?<br>><br>> For coarrays, there is CO_SUM. Otherwise, there the big problem of<br>> when it is profitable to use thread parallelization and when the<br>> overhead is too big. (Besides the issue how many threads the [...]
2015-01-21T14:20:46-05:00Tim Princehttps://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;f080bd8a.1501Re: fortran sum intrinsic question
https://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;be85dc34.1501
Ian D Chivers wrote:<br>> Jane and I are writing some new examples<br>> for the next edition of the book<br>> and have been benchmarking an openmp<br>> summation example and comparing the timing<br>> against the sum intrinsic.<br>><br>> are we likely to see parallel<br>> versions of any of the intrinsics?<br><br>For coarrays, there is CO_SUM. Otherwise, there the big problem of when<br>it is profitable to use thread parallelization and when the overhead is<br>too big. (Besides the issue how many threads the user wants to have.) –<br>That's the general problem and the reason [...]
2015-01-21T20:10:20+01:00Tobias Burnushttps://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;be85dc34.1501Re: fortran sum intrinsic question
https://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;2ba3ba9a.1501
On 1/21/2015 9:05 AM, Bill Long wrote:<br>> On Jan 21, 2015, at 1:15 AM, Ian D Chivers <ian.chivers@CHIVERSANDBRYAN.CO.UK> wrote:<br>><br>>> Jane and I are writing some new examples<br>>> for the next edition of the book<br>>> and have been benchmarking an openmp<br>>> summation example and comparing the timing<br>>> against the sum intrinsic.<br>>><br>>> are we likely to see parallel<br>>> versions of any of the intrinsics?<br>> It depends on the implementation.<br>><br>> But, in general, routines that are BLAS 1 replacements will not be threaded (though very likely vectorized). Examples include SUM [...]
2015-01-21T09:52:39-05:00Tim Princehttps://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;2ba3ba9a.1501Re: fortran sum intrinsic question
https://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;681ee7b3.1501
On Jan 21, 2015, at 1:15 AM, Ian D Chivers <ian.chivers@CHIVERSANDBRYAN.CO.UK> wrote:<br><br>> Jane and I are writing some new examples<br>> for the next edition of the book<br>> and have been benchmarking an openmp<br>> summation example and comparing the timing<br>> against the sum intrinsic.<br>><br>> are we likely to see parallel<br>> versions of any of the intrinsics? [...]
2015-01-21T14:05:09+00:00Bill Longhttps://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;681ee7b3.1501Re: fortran sum intrinsic question
https://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;50d54dc6.1501
On 1/21/2015 2:15 AM, Ian D Chivers wrote:<br>> Jane and I are writing some new examples<br>> for the next edition of the book<br>> and have been benchmarking an openmp<br>> summation example and comparing the timing<br>> against the sum intrinsic.<br>><br>> are we likely to see parallel<br>> versions of any of the intrinsics?<br>><br>> Ian Chivers<br>> Jane Sleightholme<br>When you say parallel, I assume you mean threading, as opposed to omp<br>simd reduction, which ought to be close to the sum intrinsic with<br>auto-vectorization. You would not want to give up the [...]
2015-01-21T08:48:46-05:00Tim Princehttps://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;50d54dc6.1501fortran sum intrinsic question
https://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;d5f45e39.1501
Jane and I are writing some new examples<br>for the next edition of the book<br>and have been benchmarking an openmp<br>summation example and comparing the timing<br>against the sum intrinsic.<br><br>are we likely to see parallel<br>versions of any of the intrinsics?<br><br>Ian Chivers<br>Jane Sleightholme
2015-01-21T07:15:59-00:00Ian D Chivershttps://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;d5f45e39.1501Re: TS18508 collectives: synchronisation and coarray vs noncoarray variables
https://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;9b920422.1501
On Jan 15, 2015, at 4:50 AM, Anton Shterenlikht <mexas@BRIS.AC.UK> wrote:<br><br>> It is not clear to me from TS18508<br>> whether synchronisation is required<br>> before and after the invocation<br>> of a collective subroutine.<br><br>Generally not.<br><br>> Note 7.4 mentions a "partial synchronisation<br>> of invocations of a collective subroutine".<br>> But I'm not sure if this answers my question. [...]
2015-01-15T22:02:26+00:00Bill Longhttps://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;9b920422.1501TS18508 collectives: synchronisation and coarray vs noncoarray variables
https://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;b96d61ab.1501
It is not clear to me from TS18508<br>whether synchronisation is required<br>before and after the invocation<br>of a collective subroutine.<br>Note 7.4 mentions a "partial synchronisation<br>of invocations of a collective subroutine".<br>But I'm not sure if this answers my question.<br><br>Examples in A.3.1 are also confusing.<br><br>In the first example, why x and y are defined<br>as coarray variables? This fact seems to be<br>completely unused. [...]
2015-01-15T02:50:38-08:00Anton Shterenlikhthttps://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;b96d61ab.1501parallel coarray IO via Cray extension assign -m on: performance data
https://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;d07c03c1.1501
A long mail for discussion.<br>Please advise if another mailing list is more appropriate.<br><br>On Archer I'm trying to use Cray extension "assign -m on"<br>to write coarray data in parallel to a shared direct access file.<br>There's only a single non-standard subroutine:<br><br>call asnfile( trim(fname), '-m on -F system', errstat )<br><br>which sets the assign environment for file specified<br>by the character variable "fname". The key flag is<br>"-m on", which allows the same file to be connected to multiple<br>images [1]. "-F system" specifies "No library buffering". [...]
2015-01-10T15:42:15-08:00Anton Shterenlikhthttps://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;d07c03c1.1501Re: vacancies at Nag in the USA
https://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;18e226dc.1501
Thanks Phillip, I will.<br><br>-----Original Message-----<br>From: Fortran 90 List [mailto:COMP-FORTRAN-90@JISCMAIL.AC.UK] On Behalf Of<br>Phillip Helbig<br>Sent: 07 January 2015 22:23<br>To: COMP-FORTRAN-90@JISCMAIL.AC.UK<br>Subject: Re: vacancies at Nag in the USA<br><br>> I've just been contacted by Nag. They are increasing their technical<br>> support staff in the USA.<br>><br>> Here is an extract from the mail I received.<br>><br>><br>> If you know anyone who may be interested Could you please pass the<br>> details on. [...]
2015-01-08T10:12:15-00:00Ian Chivershttps://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;18e226dc.1501Re: vacancies at Nag in the USA
https://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;645c113.1501
> I've just been contacted by Nag. They are increasing<br>> their technical support staff in the USA.<br>><br>> Here is an extract from the mail I received.<br>><br>><br>> If you know anyone who may be interested<br>> Could you please pass the details on.<br><br>Perhaps you should post it to comp.lang.fortran?
2015-01-07T23:23:19+01:00Phillip Helbighttps://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;645c113.1501vacancies at Nag in the USA
https://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;fa6177cf.1501
I've just been contacted by Nag. They are increasing<br><br>their technical support staff in the USA.<br><br>Here is an extract from the mail I received.<br><br>If you know anyone who may be interested<br><br>Could you please pass the details on.<br><br>Maybe a happy new year for a couple of people in the US!<br><br>Cheers<br><br>Ian Chivers<br><br>About NAG [...]
2015-01-07T15:50:29-00:00Ian Chivershttps://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;fa6177cf.1501Re: f2008: why bessel functions of only real arg?
https://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;e3540202.1412
Hi,<br><br>> On Dec 25, 2014, at 12:33 , Dick Hendrickson <dick.hendrickson@ATT.NET> wrote:<br>><br>> Unfortunately, the real (sorry) historical reason isn't very interesting.<br><br>Agreed. The conspiracies are much better reading.<br><br>><br>> Basically, someone went through the then current C math library<br>> (I forget which one) and picked out all of the intrinsics that<br>> weren't already in Fortran and just added them to chapter 13. [...]
2014-12-26T05:46:58-07:00Dan Naglehttps://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;e3540202.1412Re: f2008: why bessel functions of only real arg?
https://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;4d9a8c1b.1412
Unfortunately, the real (sorry) historical reason isn't very interesting.<br><br>Basically, someone went through the then current C math library<br>(I forget which one) and picked out all of the intrinsics that<br>weren't already in Fortran and just added them to chapter 13.<br>The argument (sorry again) was that if Fortran is the premier<br>scientific programming language, then it ought to have the<br>same capabilities as the competition. Presumably, the C<br>people did the thinking about which functions would be used<br>enough to be worth doing. [...]
2014-12-25T13:33:36-06:00Dick Hendricksonhttps://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;4d9a8c1b.1412Re: f2008: why bessel functions of only real arg?
https://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;5cddfebb.1412
From: "Van Snyder" <Van.Snyder@JPL.NASA.GOV><br>Sent: Tuesday, December 23, 2014 10:30 AM<br><br>> Even though Don Amos had published ACM TOMS algorithm 644 in 1986, with<br>> remarks to improve it in 1990 and 1995, there was sentiment that<br>> extending beyond real arguments and integer orders would have resulted<br>> in the proposal being rejected as too much work for implementers. [...]
2014-12-26T00:38:15+11:00Robin Vowelshttps://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;5cddfebb.1412Re: f2008: why bessel functions of only real arg?
https://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;adbd649b.1412
On Tue, 2014-12-23 at 04:12 -0800, Anton Shterenlikht wrote:<br>> >From: Van Snyder <Van.Snyder@JPL.NASA.GOV><br>> ><br>> >Even though Don Amos had published ACM TOMS algorithm 644 in 1986, with<br>> >remarks to improve it in 1990 and 1995, there was sentiment that<br>> >extending beyond real arguments and integer orders would have resulted<br>> >in the proposal being rejected as too much work for implementers.<br>><br>> I'm confused. 644 does indeed<br>> include algorithms for complex arguments [1,2].<br>> These went into Slatec, and I still use them,<br>> just checked ZBESJ [3] with complex args yesterday. [...]
2014-12-23T10:17:01-08:00Van Snyderhttps://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;adbd649b.1412Re: parallel i/o [WAS: Re: f2008: why bessel functions of only real arg?]
https://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;1668f9f1.1412
On Dec 23, 2014, at 7:47 AM, Anton Shterenlikht <mexas@BRIS.AC.UK> wrote:<br><br>>> From: Bill Long <longb@CRAY.COM><br>>>><br>>>> 1 UK-12 J3/14-174 Allow a file to be connected to more than one unit<br>>>> at one time 8-2-5<br>>>><br>>>> This sounds like parallel I/O, which I thought was<br>>>> decisively ruled out of the next revision. Am I wrong?<br>>><br>>> The change was to make it processor dependent whether this is allowed, rather than strictly prohibited as was the case previously. There are no rules specified for how this works. However, it is certainly reasonable and straightforward to have [...]
2014-12-23T15:45:20+00:00Bill Longhttps://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;1668f9f1.1412parallel i/o [WAS: Re: f2008: why bessel functions of only real arg?]
https://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;781948e1.1412
>From: Bill Long <longb@CRAY.COM><br>>><br>>> 1 UK-12 J3/14-174 Allow a file to be connected to more than one unit<br>>> at one time 8-2-5<br>>><br>>> This sounds like parallel I/O, which I thought was<br>>> decisively ruled out of the next revision. Am I wrong?<br>><br>>The change was to make it processor dependent whether this is allowed, rather than strictly prohibited as was the case previously. There are no rules specified for how this works. However, it is certainly reasonable and straightforward to have a read-only file connected on multiple images, and this has been done in [...]
2014-12-23T05:47:46-08:00Anton Shterenlikhthttps://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;781948e1.1412Re: f2008: why bessel functions of only real arg?
https://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;8b4fd9d0.1412
On Dec 23, 2014, at 5:49 AM, Anton Shterenlikht <mexas@BRIS.AC.UK> wrote:<br><br>>> From: John Reid <John.Reid@STFC.AC.UK><br>>>><br>>>> Are there any plans to extend these intrinsics<br>>>> to accept complex args?<br>>>><br>>><br>>> No. The list of extensions beyond those in the two TSs (on further<br>>> interoperability and further coarray features) is in WG5 document N2023.<br>><br>> The first item on that list is<br>><br>> 1 UK-12 J3/14-174 Allow a file to be connected to more than one unit<br>> at one time 8-2-5<br>><br>> This sounds like parallel I/O, which I thought was<br>> [...]
2014-12-23T13:31:40+00:00Bill Longhttps://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;8b4fd9d0.1412Re: f2008: why bessel functions of only real arg?
https://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;be8e4215.1412
>From: Van Snyder <Van.Snyder@JPL.NASA.GOV><br>><br>>Even though Don Amos had published ACM TOMS algorithm 644 in 1986, with<br>>remarks to improve it in 1990 and 1995, there was sentiment that<br>>extending beyond real arguments and integer orders would have resulted<br>>in the proposal being rejected as too much work for implementers.<br><br>I'm confused. 644 does indeed<br>include algorithms for complex arguments [1,2].<br>These went into Slatec, and I still use them,<br>just checked ZBESJ [3] with complex args yesterday. [...]
2014-12-23T04:12:49-08:00Anton Shterenlikhthttps://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;be8e4215.1412Re: f2008: why bessel functions of only real arg?
https://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;c98370ff.1412
>From: John Reid <John.Reid@STFC.AC.UK><br>>><br>>> Are there any plans to extend these intrinsics<br>>> to accept complex args?<br>>><br>><br>>No. The list of extensions beyond those in the two TSs (on further<br>>interoperability and further coarray features) is in WG5 document N2023.<br><br>The first item on that list is<br><br>1 UK-12 J3/14-174 Allow a file to be connected to more than one unit<br>at one time 8-2-5 [...]
2014-12-23T03:49:01-08:00Anton Shterenlikhthttps://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;c98370ff.1412Re: f2008: why bessel functions of only real arg?
https://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;6bf1b0c5.1412
On Mon, 2014-12-22 at 03:30 -0800, Anton Shterenlikht wrote:<br>> Surprised to see that the new f2008 Bessel<br>> functions cannot take complex arguments.<br>> If somebody lobbied for these to be put in<br>> the standard, they should've insisted on<br>> full complex capability. With only real<br>> argument the usefulness of these new intrinsics<br>> is severely limited. [...]
2014-12-22T15:30:17-08:00Van Snyderhttps://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;6bf1b0c5.1412Re: f2008: why bessel functions of only real arg?
https://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;13b7cb45.1412
Anton Shterenlikht wrote:<br>> Surprised to see that the new f2008 Bessel<br>> functions cannot take complex arguments.<br>> If somebody lobbied for these to be put in<br>> the standard, they should've insisted on<br>> full complex capability. With only real<br>> argument the usefulness of these new intrinsics<br>> is severely limited.<br>><br>> Are there any plans to extend these intrinsics<br>> to accept complex args?<br>> [...]
2014-12-22T18:57:06+00:00John Reidhttps://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;13b7cb45.1412f2008: why bessel functions of only real arg?
https://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;2213c0ec.1412
Surprised to see that the new f2008 Bessel<br>functions cannot take complex arguments.<br>If somebody lobbied for these to be put in<br>the standard, they should've insisted on<br>full complex capability. With only real<br>argument the usefulness of these new intrinsics<br>is severely limited.<br><br>Are there any plans to extend these intrinsics<br>to accept complex args?<br><br>Thanks<br><br>Anton
2014-12-22T03:30:39-08:00Anton Shterenlikhthttps://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;2213c0ec.1412Re: Question regarding behavior under assignment
https://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;ad316402.1412
Tom Clune wrote:<br>> In the program below, I believe that the finally print statement should<br>> return true. I have attempted to change the value of the target of a<br>> pointer through default assignment. For the three compilers that I<br>> have, 2 return .true. for the 2nd print, and one returns .false. for the<br>> 2nd print. Before I submit a bug report, I’d like to verify that my<br>> expectations on behavior are correct. [...]
2014-12-20T11:22:27+00:00John Reidhttps://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;ad316402.1412Re: Question regarding behavior under assignment
https://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;d935a228.1412
I tried the code with compilers from 4 different vendors and all 4 returned T for the second test. An ordinary assignment should not cause the pointer association of the variable to change.<br><br>Cheers,<br>Bill<br><br>On Dec 19, 2014, at 12:21 PM, Tom Clune <Thomas.L.Clune@NASA.GOV> wrote:<br><br>> In the program below, I believe that the finally print statement should return true. I have attempted to change the value of the target of a pointer through default assignment. For the three compilers that I have, 2 return .true. for the 2nd print, and one returns .false. for the 2nd print. Before [...]
2014-12-20T01:59:24+00:00Bill Longhttps://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;d935a228.1412Question regarding behavior under assignment
https://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;c560b349.1412
In the program below, I believe that the finally print statement should return true. I have attempted to change the value of the target of a pointer through default assignment. For the three compilers that I have, 2 return .true. for the 2nd print, and one returns .false. for the 2nd print. Before I submit a bug report, I’d like to verify that my expectations on behavior are correct. [...]
2014-12-19T17:21:53-05:00Tom Clunehttps://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;c560b349.1412Re: seeking guidance on managing merged f77 and f90 code
https://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;ee8c7a09.1412
Nearly but not quite true that "Valid f77 code is valid f90 code (with<br>exception of deprecated features)". If the f77 code has a function<br>or subroutine with the same name as an f90 intrinsic that wasn't an f77<br>intrinsic, (SUM for example) then you must specify EXTERNAL SUM if you<br>use an f90 compiler but you may not have had to with an f77 one. [...]
2014-12-04T08:56:16+13:00John Harperhttps://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;ee8c7a09.1412Re: seeking guidance on managing merged f77 and f90 code
https://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;4a82888d.1412
I would add the following cautionary note: Although modernizing and re-engineering code can be very fun and rewarding, one should first make certain that the effort is warranted. From the limited description, it would seem to be easier and _safer_ to leave the f77 code more-or-less untouched. If updating does make sense, then I strongy encourage you to establish a variety of test cases to ensure that the results are preserved during transformations. Automated tools such as SPAG reduce risk, but changes should still be confirmed. [...]
2014-12-03T14:29:58-05:00Tom Clunehttps://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;4a82888d.1412Re: seeking guidance on managing merged f77 and f90 code
https://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;825f7456.1412
I would bet for option 2.<br>A judicious choice that I have seen is to encapsulate the f77 code in a<br>module, and create interfaces to the functions in the module, in order to<br>have a simpler syntax when you call the subroutines. So, instead of having<br><br>call invert_matrix(A,wrk,n,rank,B)<br><br>you have<br><br>B=invert(A)<br><br>A spaghetti subroutine is no big deal if it is standard f77, it works, and<br>one has not to modify it every week. If it works, do not touch it. [...]
2014-12-03T17:32:37+01:00Andres Legarrahttps://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;825f7456.1412Re: seeking guidance on managing merged f77 and f90 code
https://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;9e9fb41e.1412
For translating f77 spaghetti code to f77 structured code there is a program<br>from Polyhedron. Google on spag f77. If it is a one-off thing (or if you<br>qualify as educational or academic use) the trial version is free.<br>The paid for version also converts to f90. However there are other, free,<br>programs to do this: Google on convert f77 to f90
2014-12-03T17:08:36+01:00W.J. Metzgerhttps://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;9e9fb41e.1412Re: seeking guidance on managing merged f77 and f90 code
https://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;93ea4969.1412
Hello,<br>I think, that it is quite impossible to give a solid answer without<br>knowing more details. So I mention just a few thoughts about the issue:<br>How old is the code? Can you understand the semantics? I ask, because I<br>know from my own experience, that really old code can be very hard to<br>understand and convert into useful routines. (I started to learn Fortran<br>40 years ago.) It might be easier to start from scratch.<br>How well structured is the code? Converting a 10k lines spaghetti code<br>to one subroutine doesn't seem to make sense for me. If [...]
2014-12-03T16:14:45+01:00Alois Steindlhttps://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;93ea4969.1412seeking guidance on managing merged f77 and f90 code
https://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;8c9a4637.1412
I am a FORmula TRANslator (not professional programmer nor computer<br>scientist) faced with the task of taking a legacy F77 code (~10K lines) and<br>turning it into a subroutine that can be called from a to-be-written F90<br>driver code. There are a lot of different way to approach the problem with<br>two extremes possibilities as follows: [...]
2014-12-03T06:59:41-07:00bennie blackwellhttps://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;8c9a4637.1412Re: TS 18508, N2033 - question on stalled images
https://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;d9216fa.1412
On Dec 2, 2014, at 8:22 AM, Tom Clune <Thomas.L.Clune@NASA.GOV> wrote:<br><br>> Bill,<br>><br>> Regarding your last point:<br>><br>> On Dec 2, 2014, at 8:59 AM, Bill Long <longb@cray.com> wrote:<br>><br>> <snip><br>><br>>> A stalled image is not executing additional statements, at least until the other images get to the END TEAM statement, at which point the stalled image can come back to life. Again, the answer depends on the scope of “communicate”. If other images try to execute a SYNC ALL, for example, the stalled image will not participate. On the other hand, remote reference [...]
2014-12-02T17:03:40+00:00Bill Longhttps://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;d9216fa.1412Re: TS 18508, N2033 - question on stalled images
https://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;6113fce7.1412
> Operationally, a stalled image is similar to a STOPPED image.<br>> Remote reference and definition still work, but the stalled/stopped<br>> image is not executing program statements, so will not execute<br>> ones that are supposed to be executed collectively,<br>> except for END TEAM (for stalled) or STOP/END PROGRAM (for stopped).<br><br>That makes sense, thank you. [...]
2014-12-02T06:23:20-08:00Anton Shterenlikhthttps://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;6113fce7.1412Re: TS 18508, N2033 - question on stalled images
https://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;7699b826.1412
Bill,<br><br>Regarding your last point:<br><br>On Dec 2, 2014, at 8:59 AM, Bill Long <longb@cray.com> wrote:<br><br><snip><br><br>> A stalled image is not executing additional statements, at least until the other images get to the END TEAM statement, at which point the stalled image can come back to life. Again, the answer depends on the scope of “communicate”. If other images try to execute a SYNC ALL, for example, the stalled image will not participate. On the other hand, remote reference and definition of variables on a stalled image should succeed, including atomic modifications. Operationally, a stalled image is similar [...]
2014-12-02T09:22:45-05:00Tom Clunehttps://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;7699b826.1412Re: TS 18508, N2033 - question on stalled images
https://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;b1055c4d.1412
On Dec 2, 2014, at 3:19 AM, Anton Shterenlikht <mexas@BRIS.AC.UK> wrote:<br><br>> I wanted to check whether I understand the<br>> logic of TS 18508 regarding failed and stalled<br>> images.<br>><br>> My understanding is that trying to communicate<br>> with a failed image will make the invoking<br>> image stalled (sec. 5.9). Is that correct?<br>> [...]
2014-12-02T13:59:48+00:00Bill Longhttps://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;b1055c4d.1412TS 18508, N2033 - question on stalled images
https://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;45446bf9.1412
I wanted to check whether I understand the<br>logic of TS 18508 regarding failed and stalled<br>images.<br><br>My understanding is that trying to communicate<br>with a failed image will make the invoking<br>image stalled (sec. 5.9). Is that correct?<br><br>To prevent this one can use e.g. FAILED_IMAGES<br>to know if any images have failed, and then<br>avoid communicating with those (sec. 7.6.14).<br>Is that correct? [...]
2014-12-02T01:19:18-08:00Anton Shterenlikhthttps://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;45446bf9.1412Re: sync and stat_stopped_image clarification
https://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;99c42b05.1412
John, thank you. It's all clear now.<br><br>Anton
2014-12-02T00:02:23-08:00Anton Shterenlikhthttps://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;99c42b05.1412Re: sync and stat_stopped_image clarification
https://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;bad6e59d.1412
On Dec 1, 2014, at 9:13 AM, Anton Shterenlikht <mexas@BRIS.AC.UK> wrote:<br><br>>>>> The program:<br>>>>><br>>>>> use, intrinsic :: iso_fortran_env<br>>>>> implicit none<br>>>>> integer :: errstat=0<br>>>>> if ( this_image() .eq. 1 ) stop "kuku"<br>>>>> sync all ( stat=errstat )<br>>>>> if ( errstat .eq. stat_stopped_image) write (*,*) "mumu"<br>>>>> end<br>>>>><br>>>>><br>>>>> My understanding from MFE sec. 19.13.6<br>>>>> and FDIS (10-007r1) sec 8.5.7 par 2 is that<br>>>>> the correct behaviour of this program is:<br>>>>><br>>>>> 1. Image 1 initiates normal termination<br>>>>> 2. At "sync all (stat=errstat)" errstat<br>>>>> becomes defined with "stat_stopped_image"<br> [...]
2014-12-01T20:13:29+00:00Bill Longhttps://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;bad6e59d.1412Re: sync and stat_stopped_image clarification
https://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;647fe8d2.1412
Anton Shterenlikht wrote:<br>>> From: John Reid <John.Reid@STFC.AC.UK><br>>> Subject: Re: sync and stat_stopped_image clarification<br>>> To: COMP-FORTRAN-90@JISCMAIL.AC.UK<br>>><br>>> Anton Shterenlikht wrote:<br>>>> I think I might have asked this question about a year ago.<br>>>> There have been at least one new version of both Cray<br>>>> and Intel compilers since then.<br>>>> I'm still not sure what behaviour is correct.<br>>>><br>>>> The program:<br>>>><br>>>> use, intrinsic :: iso_fortran_env<br>>>> implicit none<br>>>> integer :: errstat=0<br>>>> if ( this_image() .eq. 1 ) stop "kuku"<br>>>> sync all ( stat=errstat )<br>>>> if ( errstat .eq. [...]
2014-12-01T17:43:11+00:00John Reidhttps://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;647fe8d2.1412Re: sync and stat_stopped_image clarification
https://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;7a483e3c.1412
Bill Long writes:<br><br>>> My understanding from MFE sec. 19.13.6 and FDIS (10-007r1) sec 8.5.7<br>>> par 2 is that the correct behaviour of this program is:<br>>><br>>> 1. Image 1 initiates normal termination 2. At "sync all<br>>> (stat=errstat)" errstat<br>>> becomes defined with "stat_stopped_image"<br>>> on all images, but image 1.<br>>> 3. Hence all images, but image 1, must output "mumu". [...]
2014-12-01T15:13:26+00:00Lionel, Stevehttps://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;7a483e3c.1412Re: sync and stat_stopped_image clarification
https://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;c55b81eb.1412
>>> The program:<br>>>><br>>>> use, intrinsic :: iso_fortran_env<br>>>> implicit none<br>>>> integer :: errstat=0<br>>>> if ( this_image() .eq. 1 ) stop "kuku"<br>>>> sync all ( stat=errstat )<br>>>> if ( errstat .eq. stat_stopped_image) write (*,*) "mumu"<br>>>> end<br>>>><br>>>><br>>>> My understanding from MFE sec. 19.13.6<br>>>> and FDIS (10-007r1) sec 8.5.7 par 2 is that<br>>>> the correct behaviour of this program is:<br>>>><br>>>> 1. Image 1 initiates normal termination<br>>>> 2. At "sync all (stat=errstat)" errstat<br>>>> becomes defined with "stat_stopped_image"<br>>>> on all images, but image 1.<br>>>> 3. Hence all [...]
2014-12-01T07:13:13-08:00Anton Shterenlikhthttps://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;c55b81eb.1412Re: sync and stat_stopped_image clarification
https://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;441f8293.1412
>From: John Reid <John.Reid@STFC.AC.UK><br>>Subject: Re: sync and stat_stopped_image clarification<br>>To: COMP-FORTRAN-90@JISCMAIL.AC.UK<br>><br>>Anton Shterenlikht wrote:<br>>> I think I might have asked this question about a year ago.<br>>> There have been at least one new version of both Cray<br>>> and Intel compilers since then.<br>>> I'm still not sure what behaviour is correct.<br>>><br>>> The program:<br>>><br>>> use, intrinsic :: iso_fortran_env<br>>> implicit none<br>>> integer :: errstat=0<br>>> if ( this_image() .eq. 1 ) stop "kuku"<br>>> sync all ( stat=errstat )<br>>> if ( errstat .eq. stat_stopped_image) write (*,*) "mumu"<br>>> end<br>>><br> [...]
2014-12-01T06:59:07-08:00Anton Shterenlikhthttps://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;441f8293.1412Re: sync and stat_stopped_image clarification
https://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;88948b7d.1412
On Dec 1, 2014, at 7:56 AM, John Reid <John.Reid@STFC.AC.UK> wrote:<br><br>> Anton Shterenlikht wrote:<br>>> I think I might have asked this question about a year ago.<br>>> There have been at least one new version of both Cray<br>>> and Intel compilers since then.<br>>> I'm still not sure what behaviour is correct.<br>>><br>>> The program:<br>>><br>>> use, intrinsic :: iso_fortran_env<br>>> implicit none<br>>> integer :: errstat=0<br>>> if ( this_image() .eq. 1 ) stop "kuku"<br>>> sync all ( stat=errstat )<br>>> if ( errstat .eq. stat_stopped_image) write (*,*) "mumu"<br>>> end<br>>><br>>><br> [...]
2014-12-01T14:35:08+00:00Bill Longhttps://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;88948b7d.1412Re: sync and stat_stopped_image clarification
https://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;4dd6cac2.1412
Anton Shterenlikht wrote:<br>> I think I might have asked this question about a year ago.<br>> There have been at least one new version of both Cray<br>> and Intel compilers since then.<br>> I'm still not sure what behaviour is correct.<br>><br>> The program:<br>><br>> use, intrinsic :: iso_fortran_env<br>> implicit none<br>> integer :: errstat=0<br>> if ( this_image() .eq. 1 ) stop "kuku"<br>> sync all ( stat=errstat )<br>> if ( errstat .eq. stat_stopped_image) write (*,*) "mumu"<br>> end<br>><br>><br>> My understanding from MFE sec. 19.13.6<br>> and FDIS (10-007r1) sec [...]
2014-12-01T13:56:04+00:00John Reidhttps://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;4dd6cac2.1412sync and stat_stopped_image clarification
https://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;bfcb87a2.1412
I think I might have asked this question about a year ago.<br>There have been at least one new version of both Cray<br>and Intel compilers since then.<br>I'm still not sure what behaviour is correct.<br><br>The program:<br><br>use, intrinsic :: iso_fortran_env<br>implicit none<br>integer :: errstat=0<br>if ( this_image() .eq. 1 ) stop "kuku"<br>sync all ( stat=errstat )<br>if ( errstat .eq. stat_stopped_image) write (*,*) "mumu"<br>end [...]
2014-12-01T05:25:48-08:00Anton Shterenlikhthttps://www.jiscmail.ac.uk:443/cgi-bin/webadmin?A2=COMP-FORTRAN-90;bfcb87a2.1412