Re: [OMPI users] Bug: Disabled mpi_leave_pinned for GPUDirect and InfiniBand during run-time caused by GCC optimizations

2015-06-05 Thread Gilles Gouaillardet
i did not use the term "pure" properly. please read instead "posix_memalign is a function that does not modify any user variable" that assumption is correct when there is no wrapper, and incorrect in our case. On Saturday, June 6, 2015, George Bosilca wrote: > Based on the definition of a pure

Re: [OMPI users] Problem running simple application with g++ under FreeBSD 10.1

2015-06-05 Thread Jeff Squyres (jsquyres)
Is there a reason you're specifying OMPI_CXX=g++48? I.e., did you compile OMPI with a different C++ compiler? If so, that could be your issue -- try compiling OMPI with g++48 and then see if your app compiles and runs properly. > On Jun 5, 2015, at 3:30 PM, rhan...@gmx.de wrote: > > Hi, > >

[OMPI users] Problem running simple application with g++ under FreeBSD 10.1

2015-06-05 Thread rhannek
Hi, when trying to compile the attached program with mpiCC I get a segmentation fault on executing. I compile it with OMPI_CXX=g++48 mpicxx -g test.cpp Output on running the compiled program: ~> ./a.out zsh: segmentation fault (core dumped) ./a.out I have no idea what's wrong wit

Re: [OMPI users] Bug: Disabled mpi_leave_pinned for GPUDirect and InfiniBand during run-time caused by GCC optimizations

2015-06-05 Thread George Bosilca
Based on the definition of a pure function, two calls to the same pure function with the same arguments should return the same value. This is obviously never true for posix_memalign. I suggest we take a look at the generated code, and based on that we decide how to move forward on this. Geor