Luis,
With some low frequency we remove warnings from the code. In this
particular instance the meaning of the code is correct, the ompi_info_t
structure starts with an opal_info_t, but removing the warnings is good
policy.
In general we can either cast the ompi_info_t pointer directly to an
Luis,
you can do this:
struct ompi_info_t * info = _mpi_info_null.info;
ret = ompi_win_create_dynamic(_null->super, comm, win);
Cheers,
Gilles
On Fri, May 15, 2020 at 7:38 PM Luis via devel wrote:
>
> Hi OMPI devs,
>
> I was wondewring if this warning is expected, if not, how should we
>
Hi OMPI devs,
I was wondewring if this warning is expected, if not, how should we
internally call ompi_win_create_dynamic?
res = ompi_win_create_dynamic(MPI_INFO_NULL, comm, );
^
In file included from pnbc_osc_internal.h:40,
from
I'll put it on my to do list to write the configure logic for that, shouldn't be too difficult. Thanks for the report.Edgar___
devel mailing list
devel@lists.open-mpi.org
https://rfd.newmexicoconsortium.org/mailman/listinfo/devel
Dear Open MPI developer,
trying to compile Open MPI 2.0.1 using PGI compilers (19.9 and 16.7) we ran into
an error the root of one is not known yet, but we see also this warning:
#warning "Including liblustreapi.h is deprecated. Include lustreapi.h directly."
in the
I'm also seeing these warnings this morning:
connect/btl_openib_connect_rdmacm.c:369:5: warning: "BTL_OPENIB_RDMACM_IB_ADDR"
is not defined
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/
I think this is one of those local functions I defined. I wanted to
generalize this for all collective operations, such that its a permanent
fix. I can do this today.
Regards,
Vish
> I'll look into this...
>
> Edgar
>
> On 5/29/2012 3:24 PM, Ralph Castain wrote:
>> Not entirely sure who this
I'll look into this...
Edgar
On 5/29/2012 3:24 PM, Ralph Castain wrote:
> Not entirely sure who this might belong to, but thought I should pass it
> along - seen during an optimized build on Linux:
>
> fcoll_static_file_read_all.c: In function ‘mca_fcoll_static_file_read_all’:
>
Not entirely sure who this might belong to, but thought I should pass it along
- seen during an optimized build on Linux:
fcoll_static_file_read_all.c: In function ‘mca_fcoll_static_file_read_all’:
fcoll_static_file_read_all.c:74: warning: ‘sorted_file_offsets’ may be used
uninitialized in this
Excellent points Ken; thanks!
I expanded the FAQ entry here to include these points:
http://www.open-mpi.org/faq/?category=openfabrics#ofa-fork
On Nov 30, 2010, at 9:52 AM, Ken Cain wrote:
> Hi Jeff,
>
> We have had some recent experience with this in an Open MPI 1.4.x version and
>
Hi Jeff,
We have had some recent experience with this in an Open MPI 1.4.x
version and thought it would be useful to contribute to the discussion.
Please see below.
Jeff Squyres wrote:
On Nov 29, 2010, at 6:25 PM, George Bosilca wrote:
The main problem is that openib require to pin memory
On Nov 30 2010, Ralph Castain wrote:
Here is what one IB vendor says about the issue on their web site
(redacted to protect the innocent):
"At the time of this release, the (redacted-openib) driver has issues
with buffers sharing pages when fork( ) is used. Pinned (locked in
memory) pages
On Nov 29, 2010, at 6:25 PM, George Bosilca wrote:
> The main problem is that openib require to pin memory pages in order to take
> advantage of RMA features. There is a major issues with these pinned pages
> and fork, leading to segmentation fault in some specific cases. However, we
> only
Ananda
>
> -- PREVIOUS MESSAGE -
>
> Subject: Re: [OMPI devel] Warning on fork() disappears if I use MPI threads!!
> From: George Bosilca (bosilca_at_[hidden])
> Date: 2010-11-29 12:22:15
>
> Next message: Jeff Squyres: "Re
gt; applications and MPI applications using a RDMA based implementation of MPI
> (such as OFED's openmpi and mvapich).
george.
>
>
>
> Thanks
>
> Ananda
>
> ------ PREVIOUS MESSAGE -
>
> Subject: Re: [OMPI devel] Warning on fo
you
please elaborate on what makes forks vulnerable? May be that will guide
the developers to make an informed decision on whether to disable them
or find another alternative.
Thanks
Ananda
-- PREVIOUS MESSAGE -
Subject: Re: [OMPI devel] Warni
().
Thanks
Ananda
--- PREVIOUS MESSAGE -
Subject: Re: [OMPI devel] Warning on fork() disappears if I use MPI
threads!!
From: Jeff Squyres (jsquyres_at_[hidden])
List-Post: devel@lists.open-mpi.org
Date: 2010-11-29 14:10:44
* Next message: N.M. Maclaren
On Nov 29 2010, George Bosilca wrote:
If your code doesn't exactly what is described in the code snippet
attached to your previous email, then you can safely ignore the warning.
In fact, any fork done prior to the communication is a non-issue, but it
is difficult to identify. Therefore, we
If your code doesn't exactly what is described in the code snippet attached to
your previous email, then you can safely ignore the warning. In fact, any fork
done prior to the communication is a non-issue, but it is difficult to
identify. Therefore, we output the warning as soon as we detect a
I am posting this question again as it was sent before the long weekend
and didn't see any responses so far. Can anyone please explain the
discrepancy I am observing with the scenario explained in the post
below?
Thanks
Ananda
Sent: Tuesday, November 23, 2010 2:24 PM
To: de...@open-mpi.org
Hi
I am running into a very wierd problem.
If I initialize MPI normally ie; with MPI_Init(), and make one of the MPI
process to do "popen()" call, I get the following warning/error message:
== Message start ===
An MPI process has executed an operation involving a call to the
"fork()" system
On Oct 19, 2007, at 4:27 PM, Jennis Pruett wrote:
Here are the needed output files
ompi124...gz is the output from the configure and make,
This file was ok. You didn't include the output from "ompi_info --
all", but I think that I can infer most of what it would have said
(but not all --
22 matches
Mail list logo
