[AMBER-Developers] AMBER11 bugfix #19 is broken

From: Mark Williamson <mjw.mjw.name>
Date: Wed, 23 Nov 2011 13:59:41 +0000

Dear all,

Seeing this on a CUDA compile with the latest bug fixes (23/11/2011):

mpicc -ip -O3 -no-prec-div -xHost -DMPICH_IGNORE_CXX_SEEK
-DMPICH_IGNORE_CXX_SEEK -I/usr/local/Cluster-Apps/cuda/3.2/cuda/include
-IB40C -IB40C/KernelCommon
-I/usr/local/Cluster-Apps.nehalem/mvapich2/1.6/ofa/include -c gpu.cpp
gpu.cpp(445): error: class "_gpuContext" has no member "totalMemory"
          if (gpu->totalMemory < 2 * 1024 * 1024 * 1024)

gpu.cpp(445): warning #61: integer operation result is out of range
          if (gpu->totalMemory < 2 * 1024 * 1024 * 1024)

I think this is incorrect; totalMemory does not exist, it should either
be: totalGPUMemory or totalCPUMemory. Is this something local to me or
have these patches not been tested before being released? Secondly, the
subsequent warning sounds a bit worrying as well.

Seeing that the cruise control framework is now in place, it might be an
idea to introduce a test that automatically generates a patch from the
amber11-with-patches and at15-with-patches git branches and attempts to
apply them to the tagged amber11/at15 release branch and then builds and
tests etc. This should hopefully prevent the above from happening.



AMBER-Developers mailing list
Received on Wed Nov 23 2011 - 06:00:04 PST
Custom Search