From: ludovic.courtes@inria.fr (Ludovic Courtès)
To: Dave Love <fx@gnu.org>
Cc: 27850@debbugs.gnu.org
Subject: [bug#27850] gnu: mpi: openmpi: Don't enable thread-multiple
Date: Tue, 01 Aug 2017 11:27:45 +0200 [thread overview]
Message-ID: <87lgn3skmm.fsf@inria.fr> (raw)
In-Reply-To: <87o9s0bhro.fsf@i-ulialbion.it.manchester.ac.uk> (Dave Love's message of "Mon, 31 Jul 2017 19:09:15 +0100")
Dave Love <fx@gnu.org> skribis:
> Ludovic Courtès <ludovic.courtes@inria.fr> writes:
[...]
>>> (arguments
>>> `(#:configure-flags `("--enable-static"
>>>
>>> - "--enable-mpi-thread-multiple"
>>
>> Should we upgrade our openmpi package instead of doing this?
>
> I don't know whether they've fixed all the breakage I knew about in
> OMPI 2 or whether there's still any penalty from thread-multiple. 1.10
> seems fairly safe, but I don't have strong opinions if people think 2 is
> solid. Apart from ABI incompatibility, I assume it has the usual
> incompatibilities at the mpirun/MCA level, and that they aren't well
> documented.
ABI compatibility is normally not an issue with Guix, so I’d be in favor
of upgrading to 2.0.3. Would you like to do it?
Thanks,
Ludo’.
next prev parent reply other threads:[~2017-08-01 9:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-27 15:01 [bug#27850] gnu: mpi: openmpi: Don't enable thread-multiple Dave Love
2017-07-31 15:16 ` Ludovic Courtès
2017-07-31 18:09 ` Dave Love
2017-08-01 9:27 ` Ludovic Courtès [this message]
2017-08-01 16:06 ` Dave Love
2017-08-01 17:39 ` Ludovic Courtès
2017-08-01 20:10 ` Dave Love
2017-08-21 13:17 ` bug#27850: " Ludovic Courtès
2017-08-23 11:08 ` [bug#27850] " Dave Love
2017-08-23 21:34 ` Ludovic Courtès
2017-09-01 10:35 ` Dave Love
2017-09-01 22:10 ` Ludovic Courtès
2017-09-07 16:16 ` Dave Love
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lgn3skmm.fsf@inria.fr \
--to=ludovic.courtes@inria.fr \
--cc=27850@debbugs.gnu.org \
--cc=fx@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).