The differences are very very minor root@cluster:tpar# echo | gcc -v -E - 2>&1 | grep cc1 /usr/libexec/gcc/x86_64-redhat-linux/4.4.7/cc1 -E -quiet -v - -mtune=generic
[root@compute-0-1 ~]# echo | gcc -v -E - 2>&1 | grep cc1 /usr/libexec/gcc/x86_64-redhat-linux/4.4.6/cc1 -E -quiet -v - -mtune=generic Even I tried to compile the program with -march=amdfam10. Something like these /export/apps/siesta/openmpi-2.0.0/bin/mpifort -c -g -Os -march=amdfam10 `FoX/FoX-config --fcflags` -DMPI -DFC_HAVE_FLUSH -DFC_HAVE_ABORT -DTRANSIESTA /export/apps/siesta/siesta-4.0/Src/pspltm1.F But got the same error. /proc/cpuinfo on the frontend shows (family 21, model 2) and on the compute node it shows (family 21, model 1). >That being said, my best bet is you compile on a compute node ... gcc is there on the computes, but the NFS permission is another issue. It seems that nodes are not able to write on /share (the one which is shared between frontend and computes). An important question is that, how can I find out what is the name of the illegal instruction. Then, I hope to find the document that points which instruction set (avx, sse4, ...) contains that instruction. Is there any option in mpirun to turn on the verbosity to see more information? Regards, Mahmood
_______________________________________________ users mailing list users@lists.open-mpi.org https://rfd.newmexicoconsortium.org/mailman/listinfo/users
