>Thx for sharing, quite interesting. But does this mean, that there is no
working command line flag for gcc to switch this >off (like -march=bdver1
what Gilles mentioned) or to tell me what he thinks it should compile for?
Well that didn't work. maybe I messed somethings since I did recompile th
> Am 22.09.2016 um 17:20 schrieb Mahmood Naderan :
>
> Although this problem is not related to OMPI *at all*, I think it is good to
> tell the others what was going on. Finally, I caught the illegal instruction
> :)
>
> Briefly, I built the serial version of Siesta on the frontend and ran it
Although this problem is not related to OMPI *at all*, I think it is good
to tell the others what was going on. Finally, I caught the illegal
instruction :)
Briefly, I built the serial version of Siesta on the frontend and ran it
directly on the compute node. Fortunately, "x/i $pc" from GDB showed
Dear Gilles,
It seems that using GDB with MPI is a bit tricky. I read the FAQ about that.
Please see the post at https://gcc.gnu.org/ml/gcc-help/2016-09/msg00078.html
>i guess your gdb is also a bit too old to support all operations on a core
file
>(fwiw, i am able to do that on RHEL7)
This is
OK Gilles, let me try that. I will troubleshoot with gcc mailing list and
will come back later.
Regards,
Mahmood
___
users mailing list
users@lists.open-mpi.org
https://rfd.newmexicoconsortium.org/mailman/listinfo/users
Mahmood,
note you have to compile the source file that contains the snippet
with '-g -O0', and link with '-g -O0'
also, there was a typo in the gdb command,
please read "frame 1" instead of "frame #1"
Cheers,
Gilles
On Fri, Sep 16, 2016 at 12:53 PM, Gilles Gouaillardet
wrote:
> Mahmood,
>
> -
Mahmood,
-march=bdver1
should be ok on your nodes.
from the gcc command line, i was expecting -march=xxx, but it is
missing (your gcc might be a bit older for that)
note you have to recompile all your libs (openblas and friends) with
-march=bdver1
i guess your gdb is also a bit too old to suppor
I don't think there is anything OpenMPI can do for you here. The issue is
clearly on how you are compiling your application.
To start, you can try to compile without the --march=generic and use
something as generic as possible (i.e. only SSE2). Then if this doesn't
work for your app, do the same fo
Am 15.09.2016 um 19:54 schrieb Mahmood Naderan:
> 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/li
Excuse me, which is most suitable for me to find the name of the illegal
instruction?
--verbose
--debug-level
--debug-daemons
--debug-daemons-file
Regards,
Mahmood
___
users mailing list
users@lists.open-mpi.org
https://rfd.newmexicoconsortium.org/mail
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=ge
if gcc is installed on your compute node, you can run
echo | gcc -v -E - 2>&1 | grep cc1
and look for the -march=xxx parameter
/* you might want to compare that with your fronted */
And/or you can run
grep family /proc/cpuinfo
on your compute node
Then
man gcc
on your front end node
>From my gc
Although the CPUs are nearly the same, but the CPU flags are different.
I noticed that the frontend has fma, f16c, tch, tce, tbm and bmi1 while the
compute nodes don't have them.
I guess that since the programs were compiled on the frontend (6380), there
are some especial instructions in the optim
Ok, you can try this under gdb
info proc mapping
info registers
x /100x $rip
x /100x $eip
I remember you are running on AMD cpus that is why INTEL is only
instructions must be avoided
Cheers,
Gilles
On Thursday, September 15, 2016, Mahmood Naderan
wrote:
> disas command fails.
>
> Prog
disas command fails.
Program terminated with signal 4, Illegal instruction.
#0 0x008da76e in ?? ()
(gdb) bt
#0 0x008da76e in ?? ()
#1 0x008da970 in ?? ()
#2 0x00bfe9f8 in ?? ()
#3 0x in ?? ()
(gdb) disas
No function contains program counter for
--core=... is the right syntax, sorry about that
No need to recompile with -g, binary is good enough here
Then you need to run
disas
in gdb, to disassemble the instruction at 0x08da76e
And then, still in gdb
info maps
or
show maps
To find out the library this instruction is coming from
OpenBLAS i
16 matches
Mail list logo