Re: Stack size, and warnings


Dieter Britz wrote:
1. My recursive program now runs, but when I increase the size
of the job, I get an "IOT trap", which I am told is likely
to be stack overflow. I am using the Intel 90/95 compiler,
and I work under Suse Linux 10.1. I think I need to write
something into the .bashrc file; what should this be, please?

Add the following line
ulimit -s unlimited
to increase the stack size.


2. The routine calls itself many times, with array sections
as arguments, and I get a lot of warnings that a temporary
array was allocated. I tried to suppress these with the -w
option, but they don't go away. Why not, and how do I stop
them?
Sounds like you used runtime checking options when you compiled your
code. So it give you a warning during execution rather than
compilation. Recompile it without using "-check whatever" option.

Victor.

.

Relevant Pages

  • Re: Compiler warnings
    ... i followed your advice and no more warnings from the compiler. ... pointer, which points to 15 double* arrays, that each contain ... Since the parameters are statically defined, the array is most ...
    (comp.soft-sys.matlab)
  • Re: error when linking
    ... That means that in code, symbol "Foo" is used as an array, but compiler ... REAL FOO ...
    (comp.lang.fortran)
  • Re: Stack size, and warnings, PS
    ... to be stack overflow. ... I am using the Intel 90/95 compiler, ... and I work under Suse Linux 10.1. ... The routine calls itself many times, with array sections ...
    (comp.lang.fortran)
  • Re: Stack size, and warnings
    ... to be stack overflow. ... The routine calls itself many times, with array sections ... option and I no longer get the warnings. ... the same error, IOT trap. ...
    (comp.lang.fortran)
  • Re: Stack size, and warnings
    ... array was allocated. ... I tried to suppress these with the -w ... Are these warnings coming out at compile time or at run-time? ... Note that the compiler will generate ...
    (comp.lang.fortran)