I can't avoid this warning..

Questions regarding the compilation of VASP on various platforms: hardware, compilers and libraries, etc.


Moderators: Global Moderator, Moderator

Locked
Message
Author
haneol815

I can't avoid this warning..

#1 Post by haneol815 » Thu Jan 19, 2012 6:34 am

ifort -FR -lowercase -O1 -c wave_mpi.f90
fpp -f_com=no -free -w0 wave_high.F wave_high.f90 -DHOST=\"LinuxIFC\" -DCACHE_SIZE=12000 -DPGF90 -Davoidalloc -DNGXhalf
ifort -FR -lowercase -O1 -c wave_high.f90
fpp -f_com=no -free -w0 symmetry.F symmetry.f90 -DHOST=\"LinuxIFC\" -DCACHE_SIZE=12000 -DPGF90 -Davoidalloc -DNGXhalf
ifort -FR -lowercase -O1 -c symmetry.f90
fpp -f_com=no -free -w0 symlib.F symlib.f90 -DHOST=\"LinuxIFC\" -DCACHE_SIZE=12000 -DPGF90 -Davoidalloc -DNGXhalf
ifort -FR -lowercase -O1 -c symlib.f90
fpp -f_com=no -free -w0 lattlib.F lattlib.f90 -DHOST=\"LinuxIFC\" -DCACHE_SIZE=12000 -DPGF90 -Davoidalloc -DNGXhalf
ifort -FR -lowercase -assume byterecl -O2 -ip -ftz -c lattlib.f90
fpp -f_com=no -free -w0 random.F random.f90 -DHOST=\"LinuxIFC\" -DCACHE_SIZE=12000 -DPGF90 -Davoidalloc -DNGXhalf
ifort -FR -lowercase -assume byterecl -O2 -ip -ftz -c random.f90
fpp -f_com=no -free -w0 nonl.F nonl.f90 -DHOST=\"LinuxIFC\" -DCACHE_SIZE=12000 -DPGF90 -Davoidalloc -DNGXhalf
ifort -FR -lowercase -assume byterecl -O2 -ip -ftz -c nonl.f90
nonl.F(814): warning #7866: The statement following this DEC loop optimization directive must be an iterative do-stmt, a vector assignment, an OMP pdo-directive, or an OMP parallel-do-directive.
!DIR$ IVDEP
------^
fpp -f_com=no -free -w0 nonlr.F nonlr.f90 -DHOST=\"LinuxIFC\" -DCACHE_SIZE=12000 -DPGF90 -Davoidalloc -DNGXhalf
ifort -FR -lowercase -assume byterecl -O2 -ip -ftz -c nonlr.f90
fpp -f_com=no -free -w0 nonl_high.F nonl_high.f90 -DHOST=\"LinuxIFC\" -DCACHE_SIZE=12000 -DPGF90 -Davoidalloc -DNGXhalf
ifort -FR -lowercase -assume byterecl -O2 -ip -ftz -c nonl_high.f90
fpp -f_com=no -free -w0 dfast.F dfast.f90 -DHOST=\"LinuxIFC\" -DCACHE_SIZE=12000 -DPGF90 -Davoidalloc -DNGXhalf
ifort -FR -lowercase -assume byterecl -O2 -ip -ftz -c dfast.f90
fpp -f_com=no -free -w0 choleski2.F choleski2.f90 -DHOST=\"LinuxIFC\" -DCACHE_SIZE=12000 -DPGF90 -Davoidalloc -DNGXhalf
ifort -FR -lowercase -assume byterecl -O2 -ip -ftz -c choleski2.f90
fpp -f_com=no -free -w0 mix.F mix.f90 -DHOST=\"LinuxIFC\" -DCACHE_SIZE=12000 -DPGF90 -Davoidalloc -DNGXhalf
ifort -FR -lowercase -assume byterecl -O2 -ip -ftz -c mix.f90
fpp -f_com=no -free -w0 hamil.F hamil.f90 -DHOST=\"LinuxIFC\" -DCACHE_SIZE=12000 -DPGF90 -Davoidalloc -DNGXhalf
ifort -FR -lowercase -assume byterecl -O2 -ip -ftz -c hamil.f90
hamil.F(1652): warning #7866: The statement following this DEC loop optimization directive must be an iterative do-stmt, a vector assignment, an OMP pdo-directive, or an OMP parallel-do-directive.
!DIR$ IVDEP
------^
fpp -f_com=no -free -w0 xcgrad.F xcgrad.f90 -DHOST=\"LinuxIFC\" -DCACHE_SIZE=12000 -DPGF90 -Davoidalloc -DNGXhalf
ifort -FR -lowercase -assume byterecl -O2 -ip -ftz -c xcgrad.f90
fpp -f_com=no -free -w0 xcspin.F xcspin.f90 -DHOST=\"LinuxIFC\" -DCACHE_SIZE=12000 -DPGF90 -Davoidalloc -DNGXhalf
ifort -FR -lowercase -assume byterecl -O2 -ip -ftz -c xcspin.f90
fpp -f_com=no -free -w0 potex1.F potex1.f90 -DHOST=\"LinuxIFC\" -DCACHE_SIZE=12000 -DPGF90 -Davoidalloc -DNGXhalf
ifort -FR -lowercase -assume byterecl -O2 -ip -ftz -c potex1.f90
fpp -f_com=no -free -w0 potex2.F potex2.f90 -DHOST=\"LinuxIFC\" -DCACHE_SIZE=12000 -DPGF90 -Davoidalloc -DNGXhalf
ifort -FR -lowercase -assume byterecl -O2 -ip -ftz -c potex2.f90
fpp -f_com=no -free -w0 constrmag.F constrmag.f90 -DHOST=\"LinuxIFC\" -DCACHE_SIZE=12000 -DPGF90 -Davoidalloc -DNGXhalf

I succeeded a few times to make vasp but I can't avoid this warning. and even if it's done, It doesn't work properly.

Although I've used many blas and lapack, the warning always occurs.

I'm using vasp.5.2.12

Thank you for reading.
Last edited by haneol815 on Thu Jan 19, 2012 6:34 am, edited 1 time in total.

support_vasp
Global Moderator
Global Moderator
Posts: 1817
Joined: Mon Nov 18, 2019 11:00 am

Re: I can't avoid this warning..

#2 Post by support_vasp » Wed Sep 04, 2024 12:40 pm

Hi,

We're sorry that we didn’t answer your question. This does not live up to the quality of support that we aim to provide. The team has since expanded. If we can still help with your problem, please ask again in a new post, linking to this one, and we will answer as quickly as possible.

Best wishes,

VASP


Locked