 |
forums.silverfrost.com Welcome to the Silverfrost forums
|
View previous topic :: View next topic |
Author |
Message |
colt1954
Joined: 21 Dec 2010 Posts: 81
|
Posted: Fri Jul 10, 2020 9:12 am Post subject: New compilation - array problems |
|
|
Hi, I have just recompiled/built a programme a wrote in F95 in 2011/2014 it seems fine expect it not passing a multi dimensional array from a subroutine to another subroutine, its values are zero. ok I am still using the common block method but it does not appear to complain enough, i do get warnings e.g. floating point concerns, but it does prevent compilation it runs except i have these arrays that were zeroed...no good of course. |
|
Back to top |
|
 |
PaulLaidler Site Admin
Joined: 21 Feb 2005 Posts: 8210 Location: Salford, UK
|
Posted: Fri Jul 10, 2020 10:45 am Post subject: |
|
|
If you can post a short program that illustrates the failure then someone may be able to help you. |
|
Back to top |
|
 |
colt1954
Joined: 21 Dec 2010 Posts: 81
|
Posted: Fri Jul 10, 2020 3:56 pm Post subject: Re: |
|
|
PaulLaidler wrote: | If you can post a short program that illustrates the failure then someone may be able to help you. |
PROGRAM ETA
WINAPP
DIMENSION PXYZ(3),PRPM(10),PRESS(10,8,721),PMEAN(10,1,721)
COMPLEX GENG(58,721),DIS(512,3,6),X(512,3,6),KE(6,3),TFC(512,3,6)
COMMON /INTG1/ NPT,NCYL,NBRG,IGRP,IANG( ,NPOS,ORMS
COMMON /REAL1/ RPM,P(8,721),BDIS(9),WR(9),RALPH(9),F1(9),F2(9),F3(9),F4(9),WROT,WREC,R,CL,D,PMOD( ,TILT,DVEE,TDIS(9),GR
COMMON /REAL2/ COG(3),EM,SM(6),TCOG(3)
COMMON /REAL3/ THETA(2,721)
COMMON /COMP1/ GENG
COMMON /COMP2/DIS,X,KE,TFC
........
The key function GENG is referenced in several subroutines...as COMMON/COMP1/GENG.... see example below
SUBROUTINE ENGINE
COMPLEX GENG(58,721)
COMMON /INTG1/ NPT,NCYL,NBRG,IGRP,IANG( ,NPOS,NRPM
COMMON /REAL1/ RPM,P(8,721),BDIS(9),WR(9),RALPH(9),F1(9),F2(9),F3(9),F4(9),WROT,WREC,R,CL,D,PMOD( ,TILT,DVEE,TDIS(9),GR
COMMON /REAL3/ THETA(2,721)
COMMON /COMP1/ GENG
COMMON /ENGR1/ FACTR,FIC(721),YM(8,721),FANG( ...
I am getting zeros...in GENG.
In earlier compilations e.g. 2014 This was fine...now it�s not |
|
Back to top |
|
 |
colt1954
Joined: 21 Dec 2010 Posts: 81
|
Posted: Fri Jul 10, 2020 10:49 pm Post subject: Re: New compilation - array problems |
|
|
colt1954 wrote: | Hi, I have just recompiled/built a programme a wrote in F95 in 2011/2014 it seems fine expect it not passing a multi dimensional array from a subroutine to another subroutine, its values are zero. ok I am still using the common block method but it does not appear to complain enough, i do get warnings e.g. floating point concerns, but it does prevent compilation it runs except i have these arrays that were zeroed...no good of course. |
Further to the above is there anyway to compare how the latest compiler has changed since the new compiled version of my old code seems not to work fully.. though the program runs it does not return a key array variable's values correctly, just zeros. So should the compiler flag up the unacceptable condition? Hope this make some sense |
|
Back to top |
|
 |
DanRRight
Joined: 10 Mar 2008 Posts: 2923 Location: South Pole, Antarctica
|
Posted: Sat Jul 11, 2020 4:30 am Post subject: |
|
|
Compiler became since that time only deeper picky at user errors. Compile all files with /undef and use SDBG debugger. In debugger there exist options to stop at the place of first use or first change of specific variable. Try to use them to find which place zeroizes your array |
|
Back to top |
|
 |
PaulLaidler Site Admin
Joined: 21 Feb 2005 Posts: 8210 Location: Salford, UK
|
Posted: Sat Jul 11, 2020 8:01 am Post subject: |
|
|
colt1954
If you use a) the same code b) the same data and c) the same FTN95 command line arguments, then you can expect to get the same results as before. If you change any of these then it may not "work" for various reasons.
The thing to do is to first reproduce exactly what you did before and then progress in small step changes.
I am puzzled by what appears in your code as an emoticon (you have an option to suppress them when you post). If it means the presence of a colon then how does that work? |
|
Back to top |
|
 |
LitusSaxonicum
Joined: 23 Aug 2005 Posts: 2402 Location: Yateley, Hants, UK
|
Posted: Sat Jul 11, 2020 1:14 pm Post subject: |
|
|
You say you wrote it 'in F95'. Did you use FTN95, or some other compiler?
As Paul notes, what appears as an emoticon is the combination of [colon : ] and [right bracket ) ], and that wouldn't have worked in 2011-14, just like it doesn't now.
Eddie |
|
Back to top |
|
 |
colt1954
Joined: 21 Dec 2010 Posts: 81
|
Posted: Sat Jul 11, 2020 2:37 pm Post subject: Re: |
|
|
PaulLaidler wrote: | colt1954
If you use a) the same code b) the same data and c) the same FTN95 command line arguments, then you can expect to get the same results as before. If you change any of these then it may not "work" for various reasons.
The thing to do is to first reproduce exactly what you did before and then progress in small step changes.
I am puzzled by what appears in your code as an emoticon (you have an option to suppress them when you post). If it means the presence of a colon then how does that work? |
Oh no, ignore not sure how they crept in i can assure you no such things exist in the code |
|
Back to top |
|
 |
colt1954
Joined: 21 Dec 2010 Posts: 81
|
Posted: Sat Jul 11, 2020 2:39 pm Post subject: Re: |
|
|
DanRRight wrote: | Compiler became since that time only deeper picky at user errors. Compile all files with /undef and use SDBG debugger. In debugger there exist options to stop at the place of first use or first change of specific variable. Try to use them to find which place zeroizes your array |
Sorry what's /undef....please, and how do you use the SDBG exactly |
|
Back to top |
|
 |
Kenneth_Smith
Joined: 18 May 2012 Posts: 813 Location: Hamilton, Lanarkshire, Scotland.
|
|
Back to top |
|
 |
DanRRight
Joined: 10 Mar 2008 Posts: 2923 Location: South Pole, Antarctica
|
Posted: Sun Jul 12, 2020 7:15 am Post subject: |
|
|
Suppose you have the program aaa.f95
Code: | a=1
b=a*c
Print*, 'b=', b
END |
You compile it
Code: | FTN95 aaa.f95 /link /debug /undef |
You can just run the program as usual and get error report in the form of crash but better run it via debugger and see all the variables
Use F7 and F6 keys to see the execution step by step or just run to the error.
/undef and /full_undef are the most powerful debugging options
Inside debugger there exist prompts how to set debugger to stop on first use of any variable (or similarly stop on any change by the code of specific variable). Point with mouse on any variable and use right mouse button for that. All that is intuitive and does not need any guide, just try and see
Last edited by DanRRight on Sun Jul 12, 2020 6:16 pm; edited 1 time in total |
|
Back to top |
|
 |
Kenneth_Smith
Joined: 18 May 2012 Posts: 813 Location: Hamilton, Lanarkshire, Scotland.
|
|
Back to top |
|
 |
DietmarSiepmann
Joined: 03 Jun 2013 Posts: 279
|
Posted: Mon Jul 13, 2020 9:43 am Post subject: |
|
|
colt1954,
some more remarks:
it might be worthwhile knowing the version of ftn95 used for your compile/linking step (which is printed if executing command ftn95 in a Windows cmd window);
to get more information about ftn95 I often use the ftn95 online help window (by executing command "ftn95 --help" in a Windows cmd window);
in order to see what is displayed to the forum before submitting a post I often use the "Preview" button (and in most cases I do some corrections to my posts before finally submitting them
Regards,
Dietmar |
|
Back to top |
|
 |
colt1954
Joined: 21 Dec 2010 Posts: 81
|
Posted: Mon Jul 13, 2020 10:28 am Post subject: Re: |
|
|
DanRRight wrote: | Suppose you have the program aaa.f95
Code: | a=1
b=a*c
Print*, 'b=', b
END |
You compile it
Code: | FTN95 aaa.f95 /link /debug /undef |
You can just run the program as usual and get error report in the form of crash but better run it via debugger and see all the variables
Use F7 and F6 keys to see the execution step by step or just run to the error.
/undef and /full_undef are the most powerful debugging options
Inside debugger there exist prompts how to set debugger to stop on first use of any variable (or similarly stop on any change by the code of specific variable). Point with mouse on any variable and use right mouse button for that. All that is intuitive and does not need any guide, just try and see |
Hi Dan but where do you type: FTN95 aaa.f95 /link /debug /undef
i use the rebuild option not sure how you invike the above are you suggeting you do it in command mode? |
|
Back to top |
|
 |
colt1954
Joined: 21 Dec 2010 Posts: 81
|
Posted: Mon Jul 13, 2020 10:42 am Post subject: More on compilation problem |
|
|
Guys you have been so helpful.
I have found something with my code its not a zero array problem per se. lets explain: Its a rigid engine vibration program and it appears that the rotational responses are zero - ie the 'rotation variables are zero' and i am now looking at this - it is only working for one translation response e.g. Z direction...but the point is I have not knowingly changed any of the code, only re-compiled hence this problem now!
Couple of ideas:
1) Can you un-compile to get back to the original source of the one that does not work?
2) If so is there a way to compare codes side by side in an automated way without trawling through what is a very large programme. |
|
Back to top |
|
 |
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
Powered by phpBB © 2001, 2005 phpBB Group
|