[Wien] ifort (ifc) 8.0 and mkl 6.1

[Mahmoud Payami]

Dear All,

Thanks to the suggestions of Lutz Rauscher, which is added in this message,
I managed to compile Wien2k_04 successfully, just by removing the "static"
option; and also performed the command:
ulimit -s unlimited
However, the following lines appeared:

----------------------------------------------------------------------------
-----
Stack trace terminated abnormally.

mixer              0804A8DC  Unknown               Unknown  Unknown
mixer              0806625E  Unknown               Unknown  Unknown
mixer              08066797  Unknown               Unknown  Unknown
mixer              0807EC25  Unknown               Unknown  Unknown
mixer              40137DFC  Unknown               Unknown  Unknown
mixer              40138FCE  Unknown               Unknown  Unknown
Image              PC        Routine            Line        Source
forrtl: severe (174): SIGSEGV, segmentation fault occurred
 CORE  END
 LAPW2 END
 LAPW1 END
 LAPW0 END
----------------------------------------------------------------------------
-----

Any suggestion is highly appreciated.

Best Regards,
M. Payami



----- Original Message ----- 
From: "Lutz Rauscher" <rauscher at qms.cache.waseda.ac.jp>
To: <wien at zeus.theochem.tuwien.ac.at>
Sent: Wednesday, February 04, 2004 1:49 PM
Subject: [Wien] ifort (ifc) 8.0 and mkl 6.1


> Dear All,
>
> I hope has not yet been discussed; I lost track a bit... I compiled Wien2k
> with ifort (ifc) 8.0 and mkl 6.1 and there are two "known issues" that
need
> to be considered if you do so:
>
> 1. ifort troubles with a static linked pthreat library. The easiest thing
is
> just to omit the -static linker option. If you really need the static
> linking there's another workaround described in the release note involving
> the nptl-devel package, but I didn't try.
>
> 2. For larger cases you get segmentation faults anyway, because ifort
"[...]
> allocates more temporaries on the stack than previous Intel Fortran
> compilers. If a program has inadequate stack space at runtime, it will
> terminate with a Segmentation fault or Signal 11. The stack space can be
> increased with the ulimit -s unlimited command (in bash shell) or limit
> stacksize unlimited (in csh shell)".
>
> That does the trick and Wien2k seems to run smooth - at least for my
cases.
> It would be interesting whether anybody has still problems.
> Its maybe worth to try, it seems to be quite fast: I measured 228s for the
> benchmark test on a 3.2 GHz P4, 512kB L2 with 400MHz dual bus memory.
>
> Regards, Lutz
>
>
> _______________________________________________
> Wien mailing list
> Wien at zeus.theochem.tuwien.ac.at
> http://zeus.theochem.tuwien.ac.at/mailman/listinfo/wien
>