[MITgcm-support] LOOP WAS VECTORIZED
q li
qliuri at yahoo.com
Mon Jul 19 23:22:09 EDT 2010
Hi all,
Recently I am using the MITgcm at a cluster with AMD64 cpu, together with ifort
(9.1.040) and mpich (2.1.2). I received a message called "remark: LOOP WAS
VECTORIZED". I googled "MITgcm remark: LOOP WAS VECTORIZED" and nothing feeds
back. I am wondering if any MITgcmer had this problem. Then I keep searching and
found someone said this is related to "optimization switches", then he suggest
to add "-ftz -ip -ipo -parallel -axP " (see
http://lists.apple.com/archives/fortran-dev/2006/Apr/msg00035.html). It does not
show these "remark" messages immediately, but they show up together in the end
of "make". I do the internal wave test in both way. The results "look" fine and
exactly same.
My question is
(1) Are these "remark" messages a warning or error? Will they influence my
calculation?
(2) Any way to avoid it?
(3) Is any special setting for me to use Intel's ifort on a AMD64 cluster?
$ mpif77 -w95 -W0 -WB -convert big_endian -assume byterecl -fPIC -O2 -align -xW
-ip -c chksum_tiled.f
chksum_tiled.f(722) : (col. 9) remark: LOOP WAS VECTORIZED.
chksum_tiled.f(733) : (col. 9) remark: LOOP WAS VECTORIZED.
$ mpif77 -w95 -W0 -WB -convert big_endian -assume byterecl -fPIC -O2 -align -xW
-ip -c -ftz -ip -ipo -parallel -axP chksum_tiled.f
Regards,
Li
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mitgcm.org/pipermail/mitgcm-support/attachments/20100719/52f4bfcf/attachment.htm>
More information about the MITgcm-support
mailing list