Hi,
The reason you cannot find it is because it actually is not define as such. The
PMPI interface is defined as the profiling interface. The principle is you have
the real symbol in your shared library that is PMPI_Send, with a weak alias
being MPI_Send. So, if a third party want to intercept
need for a cid if all you hold
is a group reference. Plus, a communicator has a bunch of other state
(collective modules handles, etc.) that aren’t necessarily needed by a
window.
Brian
On Nov 29, 2017, at 5:57 AM, Clement FOYER <mailto:clement.fo...@gmail.com>> wrote:
Hi Brian,
Hi Brian,
Even if I see your point, I don't think a user request de free the
communicator should necesserily lead to the communicator being deleted,
only released from one hold, and available to be disposed by the
library. I don't see objection to have the library keep a grab on these
communi
As George pointed out earlier, there is no construct in C able to tell
you if a random number is a valid C pointer, i.e., is a valid memory
address. -1, once casted to a pointer, would correspond to the adress
0x...f .
It would probably be better to ajust the initial code in order to use
ction recursively call itself as first statement,
without modifying any argument. This function is defined in
ompi/mca/osc/pt2pt/osc_pt2pt_frag.h line 169.
Is it the normal behaviour? How is it supposed to stop from recursively
call itself?
Cheers,
Clement
ction recursively call itself as first statement,
without modifying any argument. This function is defined in
ompi/mca/osc/pt2pt/osc_pt2pt_frag.h line 169.
Is it the normal behaviour? How is it supposed to stop from recursively
call itself?
Cheers,
Clement
ned long or unsigned
long long, and thus it should be possible to use them in the same cases
unsigned long int and unsigned long long int are ?
Thenk you in advance for your answer,
Clement FOYER
___
devel mailing list
devel@list
Thank you Gilles for your answer.
Pull request #3023 added.
Cheers,
Clément FOYER
On 02/23/2017 03:35 PM, gil...@rist.or.jp wrote:
Thanks Clement,
the best way is to make a pull request.
your commit must contain a
Signed-off-by: ...
line in order to be considered for inclusion.
and that can
Hi everyone,
I found a typo in the comment for the opal_list_item_compare_fn_t
typedef (opal/class/opal_list.h:877). It says the functions should
return "11" instead of "-1" for a < b. Should I open a issue on the
github, or is there already a thread where to add minor typo mistakes,
or shoul
ist_next.opal_list_next.opal_list_next.opal_list_next.opal_list_next.opal_list_next.opal_list_next)).btl_module
$52 = (mca_btl_base_module_t *) 0x0
Sorry for the noise in your mail boxes. I thought it may have been
valuable informations to know where these pointers point to.
Clement FOYER
On 0
Hi everyone,
I've been facing issues with the creations of windows (MPI_Win_create).
Maybe it's an already known issue, or maybe you will be able to tell me
where to check to find the problem.
I've been developping some benchmark to evaluate the overhead of a
monitoring module. Everything wo
eters
INTEGER comm
will be replaced (modulo the typos) with
MPI_Comm c_comm;
MPI_Fint *comm;
c_comm = MPI_Comm_f2c(*comm);
And so on, that is why Fortran wrapper is preferred,
plus there might be over caveats with Fortean 2008
Cheers,
Gilles
On Monday, December 12, 2016, Clement FOYER wrote:
Hello everyone,
I have been trying to redirect MPI_Init and MPI_Finalize calls from a
FORTRAN application (the CG benchmark from NAS Parallel Benchmarks). It
appears that in the fortran application the MPI_Init function signature
is "mpi_init_", whereas in my shared object it is MPI_Init. How
Hi everyone,
I was wondering if it was possible to remove an element while iterating
over the elements of a hashtable. As saw that it wasn't while using the
OPAL_HASHTABLE_FOREACH macro, and I suppose it's because of the possible
loss of the current next element. But how about if the element h
Gilles
On Wednesday, October 26, 2016, Clement FOYER
wrote:
Hi everyone,
I've got two Makefile configuration problems, and I thought maybe someone
here could give me hints to resolve them.
I've been working on a component that is part in ompi/mca/pml/comp, and
Hi everyone,
I've got two Makefile configuration problems, and I thought maybe
someone here could give me hints to resolve them.
I've been working on a component that is part in ompi/mca/pml/comp, and
part in mca/common/comp. And I don't really know which variables/target
to set in order to
16 matches
Mail list logo
