compiler/linker flags to abort array assignment (non-standard) use during run time
in [Fortran]
|
Prev: compiler/linker flags to abort array assignment (non-standard) useduring run time
Next: compiler/linker flags to abort array assignment (non-standard)use during run time
From: Michael Metcalf on 23 Apr 2008 13:39 "Fei Liu" <fei.liu(a)gmail.com> wrote in message news:funrc4$uv7$1(a)aioe.org... > Hello Group, > I am trying to come up with a list of compiler/linker options so that > when the following code is run, a run time failure is generated. Or at > least a compile time diagnosis is reported. > > The target compiler is Intel ifort. I would like to catch as many > non-standard coding practice as possible at both compile time and run > time. > > I currently use '-std -warn all -WB -Winline -traceback' but it does not > catch the error in the following code. > In the general case your 'error' cannot be detected at either compile- or run-time, other than by wearing your seat-belt: if(size(x) /= size(y)) print *, 'Ring the alarm bells!' Regards, Mike Metcalf
From: Gordon Sande on 23 Apr 2008 14:30 On 2008-04-23 14:53:14 -0300, Fei Liu <fei.liu(a)gmail.com> said: > Michael Metcalf wrote: >> "Fei Liu" <fei.liu(a)gmail.com> wrote in message news:funrc4$uv7$1(a)aioe.org... >>> Hello Group, >>> I am trying to come up with a list of compiler/linker options so that >>> when the following code is run, a run time failure is generated. Or at >>> least a compile time diagnosis is reported. >>> >>> The target compiler is Intel ifort. I would like to catch as many >>> non-standard coding practice as possible at both compile time and run >>> time. >>> >>> I currently use '-std -warn all -WB -Winline -traceback' but it does >>> not catch the error in the following code. >>> >> In the general case your 'error' cannot be detected at either compile- >> or run-time, other than by wearing your seat-belt: >> >> if(size(x) /= size(y)) print *, 'Ring the alarm bells!' >> >> Regards, >> >> Mike Metcalf >> > Thanks, in general I am looking for a set of stricter compiler/linker > options that will help diagnose potential problems. > > Fei There is always the option of usng a compiler which is intended to support debugging. Multiple compilers is always a good way to catch dodgy coding. The Salford/Siverfrost compiler for Windows is one. Another is NAGWare V5 which supports multiple platforms. Salford is free for personal use. NAG is not. Lahey/Fujitsu is also good and not free. Windows and Linux if I recall correctly. Checking for out of range subscripts for assumed size ("*" form) arrays, and some other tings, may not be compatible with third party precompiled libraries because of the extra information that is carried at run time. Turning subscript checking and undefined variable checking on will cause things to run slower. Some folks prefer slow correct results to fast wrong ones. Once the code is fully debugged you are free to turn the training wheels off.
From: Tobias Burnus on 23 Apr 2008 14:33 On Apr 23, 7:24 pm, Fei Liu <fei....(a)gmail.com> wrote: > Hello Group, > I am trying to come up with a list of compiler/linker options so that > when the following code is run, a run time failure is generated. Or at > least a compile time diagnosis is reported. Try turning on the bounds checking, e.g. -fbounds-check, -C, -C=all, - check all, ... (I don't know this option is called for your compiler.) Tobias
From: Fei Liu on 23 Apr 2008 15:37
Tobias Burnus wrote: > On Apr 23, 7:24 pm, Fei Liu <fei....(a)gmail.com> wrote: >> Hello Group, >> I am trying to come up with a list of compiler/linker options so that >> when the following code is run, a run time failure is generated. Or at >> least a compile time diagnosis is reported. > > Try turning on the bounds checking, e.g. -fbounds-check, -C, -C=all, - > check all, ... (I don't know this option is called for your compiler.) > > Tobias Thanks, now I use -e95 -std95 -C -CB -CA -CU -warn all -WB -Winline -traceback Fei |