On Feb 16, 2009, at 9:16 PM, George Bosilca wrote:
Based on several man pages, free is capable of handling a NULL
argument. What is really puzzling is that on your system it
doesn't ...
I tried on two system a 64 bits Debian and on my MAC OS X with all
memory allocator options on, and
This should be fixed in r20576; I'll go start a new tarball build
right now...
On Feb 16, 2009, at 9:33 PM, MPI Team wrote:
ERROR: Command returned a non-zero exist status (trunk):
./configure --enable-dist
Start time: Mon Feb 16 21:26:57 EST 2009
End time: Mon Feb 16 21:33:03 EST
I am registering users for the Feb ORTE meeting (https://svn.open-mpi.org/trac/ompi/wiki/Feb09Meeting
).
Please let me know if you plan to attend but did *not* receive an
email from Cisco containing your wifi access code.
Thanks!
--
Jeff Squyres
Cisco Systems
OMPI Developers --
Ralph and I are continuing our Mercurial investigations. The dominos
are starting to fall in order nicely and it's looking pretty good that
the Open MPI project could switch away from Subversion to Mercurial if
we choose to. You can see our current list of open
The Open MPI Team, representing a consortium of research, academic,
and industry partners, is pleased to announce the release of Open MPI
version 1.2.9. This release is mainly a bug fix release over the v1.2.8
release. This is the last planned release from the 1.2 series.
We strongly recommend
I think I just did my first putback to the trunk. God help us all!
It's r20578 and feedback (e.g., "you broke everything") is appreciated,
gentle feedback even more so.
I had claimed at the in-person meeting last week that the "single queue"
approach showed no appreciable performance
I guess that if the free function supports the NULL pointer we should
do the same...
george.
On Feb 17, 2009, at 07:35 , Jeff Squyres wrote:
On Feb 16, 2009, at 9:16 PM, George Bosilca wrote:
Based on several man pages, free is capable of handling a NULL
argument. What is really
Let's say I have a combo SVN/HG workspace.
Let's say someone makes changes to the trunk. I guess I bring those
over to my combo workspace with "svn up". Yes? How then do I make the
HG side of the combo repository see those updates?
Check this wiki page out: https://svn.open-mpi.org/trac/ompi/wiki/UsingMercurial
On Feb 17, 2009, at 12:36 PM, Eugene Loh wrote:
Let's say I have a combo SVN/HG workspace.
Let's say someone makes changes to the trunk. I guess I bring those
over to my combo workspace with "svn up". Yes?
Per the call today, I ran the reduce-hang.c test on a single x86 4-
core xeon node with both 1.2.8 and 1.2.9. I see the same behavior
with both:
- none of the processes hang; they all keep iterating over MPI_REDUCE
- the iteration numbers sent to stdout are more-or-less in sync
- memory
On Feb 17, 2009, at 11:18 AM, George Bosilca wrote:
I guess that if the free function supports the NULL pointer we
should do the same...
I'll agree with that if we know for sure that free(NULL) is
universally supported. You mentioned "a few man pages" -- how
universal is this support?
I've been wading through this page over and over, but can't seem to find
this particular tidbit.
If you have the OMPI SVN repository, a combo SVN/HG area, and an HG
clone (the pictures on that web page would have you going from left to
right), then the page tells you:
1) How to populate
Ah! Sorry; I thought we had some discussion about that but perhaps it
was forgotten. :-\
Here's what I typically run to bring down changes from SVN to HG:
# Ensure all the latest hg repo changes are in the working dir
hg up
# Bring in all the SVN changes
svn up
# Refresh the .hgignore file
I can confirm it at least on MAC OS X and Linux. Based on IEEE Std
1003.1-2008, if the argument of the free function is null, no action
should occur. So I guess most POSIX compliant environments support the
NULL argument.
george.
On Feb 17, 2009, at 13:01 , Jeff Squyres wrote:
On Feb
On Feb 17, 2009, at 2:05 PM, George Bosilca wrote:
I can confirm it at least on MAC OS X and Linux. Based on IEEE Std
1003.1-2008, if the argument of the free function is null, no action
should occur. So I guess most POSIX compliant environments support
the NULL argument.
Sounds good.
Hello,
* Jeff Squyres wrote on Tue, Feb 17, 2009 at 07:01:01PM CET:
> On Feb 17, 2009, at 11:18 AM, George Bosilca wrote:
>
>> I guess that if the free function supports the NULL pointer we should
>> do the same...
>
> I'll agree with that if we know for sure that free(NULL) is universally
>
Eugene,
It appears this is a sm BTL problem. The prepare_src function can be
called with any size. The BTL should check the size against the eager
and return a descriptor that match the size requested.
george.
On Feb 17, 2009, at 20:14 , Eugene Loh wrote:
(Rich: same question as I
17 matches
Mail list logo
