Consider adding the improved description for --with-tm from 1.5.3
--with-tm(=DIR) Build TM (Torque, PBSPro, and compatible)
support,
optionally adding DIR/include, DIR/lib, and
DIR/lib64 to the search path for headers and
The help text for --with-valgrind in configure appears twice (fixed in
1.5.3)
--with-libnuma-libdir=DIR
Directory where the libnuma software is
installed
--with-valgrind(=DIR) Directory where the valgrind software is
installed
--with-memory-manager=TYPE
On May 18, 2011, at 8:32 PM, Larry Baker wrote:
> The PGI compilers have a -fast and a -fastsse option. Does OpenMPI make
> effective/safe use of SSE instructions (block moves maybe?)?
Not really. The biggest thing that we do that can take advantage of vector
instructions is memcpy, *mostly
v1.4 RMs: see the suggestion below. We have this text in trunk and v1.5; it's
a fairly straightforward patch for v1.4.
Do you want it in v1.4.4?
On May 19, 2011, at 2:54 PM, Larry Baker wrote:
> Consider adding the improved description for --with-tm from 1.5.3
>
>> --with-tm(=DIR)
Jeff,
Thanks for your reply.
I inquired the same of PGI. Dave Borer, PGI Customer Service Manager,
responded:
I believe -fast and -fastsse are identical for 64-bit compilers,
but there are some differences
with 32-bit compilers. I don't think TCP/IP based MPI routines have
better perf
This is a function of using two different subsystems that both put in their own
--with-valgrind options in different .m4 scripts. It's solved in a different
way on the trunk / v1.5. So I think we'll just have to live with it for
v1.4.x. :-\
Many thanks for all these close inspections!
On M
Anyone out there using the orte-iof tool? I very much doubt it, but wanted to
check before deleting it.
Also, do we need to retain the ability for outside tools to attach to OMPI's io
forwarding system? It's a bit of code to maintain, but I'll leave it if someone
actually intends to use this to
On May 19, 2011, at 9:46 PM, Larry Baker wrote:
> I inquired the same of PGI. Dave Borer, PGI Customer Service Manager,
> responded:
>
>> I believe -fast and -fastsse are identical for 64-bit compilers, but there
>> are some differences
>> with 32-bit compilers. I don't think TCP/IP based MP
With all the outputs from Paul and Sam, I think we'll be good.
...hmmm. Wait. I see that our 1.4.x configure *is* patched to have the extra
".". Here's the lines from configure in 1.4.3 and 1.4.4rc2:
# Portland Group C++ compiler
We're not using the tool, but we are interested in the IO forwarding framework
that allow external tools to attach/detach.
george.
On May 19, 2011, at 17:48 , Ralph Castain wrote:
> Anyone out there using the orte-iof tool? I very much doubt it, but wanted to
> check before deleting it.
>
>
On May 19, 2011, at 8:05 PM, George Bosilca wrote:
> We're not using the tool, but we are interested in the IO forwarding
> framework that allow external tools to attach/detach.
Okay - I'll leave that code intact, but remove the tool (pending anyone else's
reply). Thx!
>
> george.
>
> On M
Jeff,
I ran into some kind of link error, I think, with PGI 10.3 and OpenMPI
1.4.2 last year. I am building a new cluster and we have PGI 11.4
now. I am consulting my notes and patches from 1.4.2 to inspect 1.4.3
to see if the problems I had have been fixed. I found the .m4 files I
pat
12 matches
Mail list logo
