Re: [OMPI users] Addendum to: Assembler instruction errors for push and pop during make

2013-08-21 Thread Richard Haney
Hmmm... Thanks, Jeremiah, for the suggestion. File win_compat.h is in directory opal/win32 , a directory which by its name is supposedly concerned only with producing a 32-bit target, and so, because we are doing a build for a 64-bit target, it seems make should not be having anything to do with

Re: [OMPI users] Mixing Linux's CPU-shielding with mpirun's bind-to-core

2013-08-21 Thread John Hearns
Agree with what you say Dave. Regarding not wanting jobs to use certsin cores ie. reserving low-numbered cores for OS processes then surely a good way forward is to use a 'boot cpuset' of one or two cores and let your jobs run on the rest of the cores. You're right about cpusets being helpful wit

Re: [OMPI users] Mixing Linux's CPU-shielding with mpirun's bind-to-core

2013-08-21 Thread Dave Love
John Hearns writes: > You really should install a job scheduler. Indeed (although it's the resource management component that does the job). > There are free versions. > > I'm not sure about cpuset support in Gridengine. Anyone? Yes, but I've had reports of problems (races?) that I haven't sor

Re: [OMPI users] Mixing Linux's CPU-shielding with mpirun's bind-to-core

2013-08-21 Thread Siddhartha Jana
Hi, 1. If you use OMPI's --bind-to-core option and then re-bind yourself to > some other core, then all the memory affinity that MPI setup during > MPI_Init() will be "wrong" (possibly on a remote numa node). I would > advise against doing this. > Ah yes! Noted. > > 3. Rather that setting up c

Re: [OMPI users] Finalize() does not return

2013-08-21 Thread Eloi Gaudry
>> Is there any other information I could provide that might be useful? >You might want to audit the code and ensure that you have no pending >communications that haven't finished -- check all your sends and receives, not >just in the code, but at run-time (e.g., use an MPI profiling tool to mat

Re: [OMPI users] Problem compiling 1.7.2 on Mac OS 10.8 with gcc 4.8

2013-08-21 Thread Hugo Gagnon
My apologies; I just realized that I was compiling with the LLVM dragonegg 3.4 GCC plugin, which apparently does not support all of GCC yet. Hopefully this will be of some help to someone in the future! -- Hugo Gagnon On Wed, Aug 21, 2013, at 7:07, Bert Wesarg wrote: > Hugo, > > On Tue, Aug

Re: [OMPI users] Problem compiling 1.7.2 on Mac OS 10.8 with gcc 4.8

2013-08-21 Thread Bert Wesarg
Hugo, On Tue, Aug 20, 2013 at 6:09 PM, Hugo Gagnon wrote: > Hi, > > I'm encountering this error during "make all": > > Undefined symbols for architecture x86_64: > "___atomic_fetch_add_4", referenced from: > std::locale::locale(std::locale const&, > SpaceSeparator*) in otfprofile-cr