Re: DDASPK problem

Konstantinos Tseronis wrote:
>
> I forgot to mention that I am using Intel Fortran Compiler 8.

Oops, a crucial detail, you're using a work-in-progress compiler
unsuitable for serious work, unless living dangerously is your thing. In
short, your problem is likely with the compiler rather than with a
reasonably robust, albeit far from perfect, "daspk" code.

---
bv
------------------------------------------------------
Applied Algorithms http://sdynamix.com

.

Relevant Pages

  • Re: How so ?
    ... as s is a pointer to an array of char -- but no one ever bothers, ... and the compiler will complain in g++. ... This one actually works in VMS -- or did, ... The old "oops I forgot that extra char" problem. ...
    (microsoft.public.win32.programmer.ui)
  • Re: Oops linux 2.4.23-pre6 on amd64
    ... >>Oops, scratch that last one... ... It's invalid too as I used the original ... falling over with internal compiler errors/segfaults/etc.). ... send the line "unsubscribe linux-kernel" in ...
    (Linux-Kernel)
  • Re: Do not misuse Coverity please (Was: sound/oss/cs46xx.c: fix a check after use)
    ... > No, there is a third case: the pointer can be NULL, but the compiler ... just hope that the gcc folks know their business:) ... > with -O0, it will oops. ... send the line "unsubscribe linux-kernel" in ...
    (Linux-Kernel)
  • Re: DDASPK problem
    ... >> I forgot to mention that I am using Intel Fortran Compiler 8. ... > Oops, a crucial detail, you're using a work-in-progress compiler ...
    (sci.math.num-analysis)
  • Re: Another sizeof question
    ... so it is not evaluated by sizeof. ... Oops, yes. ... int n = 42; ... the compiler do with the result of computing xanyway? ...
    (comp.lang.c)