1. I have a simulation code which ports very well on 32-bit systems be it
parallel or serial, windows(for serial only) or linux(for both). We have
just installed Suse linux 9.3 on a Fujitsu-Siemens celsius workstation which
uses a 64 bit xeon processor. This system has also been used to configure
and install lam 7.1.1 which has passed all the lamtests eventually. The
strange thing happening now is that this same code that runs well on other
systems has been executing in a very bizarre way on the 64-bit system. For
example, it executes one mpirun and then the same code crashes with SINAL 11
(segmentation fault) in the function where data(sim parameters) is read and
set. After a few attempts it will run and crash again. Does anyone have a
clue as to what is happening? Is it a 64 bit architecture problem??
2. How can I compile the lam mpi source code and install on my 64-bit system
so that I can use the g++ -m32 to create a 32 bit executable. I am able to
compile with -m32 flags but I cannot obviously use the 64-bit lam library
file to link the object files. I know for sure I need the 32-bit library
file but how to do that is my problem :(
3. How does atomicity.h affect our executables (though this is not MPI
specific I shall be grateful if someone could fill me in). Could it be the
cause of the problem?
Thank you in advance and counting on your help
Leslie Nkansa Osei-Bonsu
Graduate Student
Computational Science and Engineering
Department of Informatics
Technische Universität München
|
