From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 77408 invoked by alias); 24 Sep 2018 10:58:24 -0000 Mailing-List: contact fortran-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: fortran-owner@gcc.gnu.org Received: (qmail 77390 invoked by uid 89); 24 Sep 2018 10:58:23 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.2 required=5.0 tests=AWL,BAYES_00,HTML_MESSAGE,KAM_LAZY_DOMAIN_SECURITY autolearn=no version=3.3.2 spammy=UD:ie, caf, CAF, is X-HELO: mail.sceal.ie Received: from mail.sceal.ie (HELO mail.sceal.ie) (83.70.207.66) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 24 Sep 2018 10:58:20 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.sceal.ie (Postfix) with ESMTP id 0FA2316ABD3; Mon, 24 Sep 2018 11:58:18 +0100 (IST) Received: from mail.sceal.ie ([127.0.0.1]) by localhost (mail.sceal.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d8zpfJJPOO8l; Mon, 24 Sep 2018 11:58:13 +0100 (IST) Received: from AlastaisLaptop2.ichec.ie (arcturus.ichec.ie [193.1.243.3]) by mail.sceal.ie (Postfix) with ESMTPSA id 5D2161694CB; Mon, 24 Sep 2018 11:58:13 +0100 (IST) Subject: Re: OpenCoarrays integration with gfortran To: Toon Moene , Jerry DeLisle , Damian Rouson Cc: Thomas Koenig , ams@codesourcery.com, Janne Blomqvist , gcc patches , gfortran References: <024e798b9539b765a1259cfc9cb2f1dc480b24ca.1536144068.git.ams@codesourcery.com> <7f5064c3-afc6-b7b5-cade-f03af5b86331@moene.org> <9290b55e-b12a-838a-5943-0c72d040dc3f@codesourcery.com> <7bef0368-f709-642b-3bb4-14cb07aaba25@netcologne.de> <594e5471-3e22-40ae-0be4-952b2c246e3a@charter.net> From: Alastair McKinstry X-Tagtoolbar-Keys: D20180924115812486 Message-ID: Date: Mon, 24 Sep 2018 10:58:00 -0000 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:60.0) Gecko/20100101 Thunderbird/60.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-SW-Source: 2018-09/txt/msg00186.txt.bz2 On 23/09/2018 10:46, Toon Moene wrote: > On 09/22/2018 01:23 AM, Jerry DeLisle wrote: > > I just installed opencoarrays on my system at home (Debian Testing): > > root@moene:~# apt-get install libcoarrays-openmpi-dev > ... > Setting up libcaf-openmpi-3:amd64 (2.2.0-3) ... > Setting up libcoarrays-openmpi-dev:amd64 (2.2.0-3) ... > Processing triggers for libc-bin (2.27-6) ... > > [ previously this led to apt errors, but not now. ] > > and moved my own installation of the OpenCoarrays-2.2.0.tar.gz out of > the way: > > toon@moene:~$ ls -ld *pen* > drwxr-xr-x 6 toon toon 4096 Aug 10 16:01 OpenCoarrays-2.2.0.opzij > drwxr-xr-x 8 toon toon 4096 Sep 15 11:26 opencoarrays-build.opzij > drwxr-xr-x 6 toon toon 4096 Sep 15 11:26 opencoarrays.opzij > > and recompiled my stuff: > > gfortran -g -fbacktrace -fcoarray=lib random-weather.f90 > -L/usr/lib/x86_64-linux-gnu/open-coarrays/openmpi/lib -lcaf_mpi > > [ Yes, the location of the libs is quite experimental, but OK for the > "Testing" variant of Debian ... ] > > I couldn't find cafrun, but mpirun works just fine: > > toon@moene:~/src$ echo ' &config /' | mpirun --oversubscribe --bind-to > none -np 20 ./a.out > Decomposition information on image    7 is    4 *    5 slabs with   23 > *   18 grid cells on this image. > Decomposition information on image    6 is    4 *    5 slabs with   23 > *   18 grid cells on this image. > Decomposition information on image   11 is    4 *    5 slabs with   23 > *   18 grid cells on this image. > Decomposition information on image   15 is    4 *    5 slabs with   23 > *   18 grid cells on this image. > Decomposition information on image    1 is    4 *    5 slabs with   23 > *   18 grid cells on this image. > Decomposition information on image   13 is    4 *    5 slabs with   23 > *   18 grid cells on this image. > Decomposition information on image   12 is    4 *    5 slabs with   21 > *   18 grid cells on this image. > Decomposition information on image   20 is    4 *    5 slabs with   21 > *   18 grid cells on this image. > Decomposition information on image    9 is    4 *    5 slabs with   23 > *   18 grid cells on this image. > Decomposition information on image   14 is    4 *    5 slabs with   23 > *   18 grid cells on this image. > Decomposition information on image   16 is    4 *    5 slabs with   21 > *   18 grid cells on this image. > Decomposition information on image   17 is    4 *    5 slabs with   23 > *   18 grid cells on this image. > Decomposition information on image   18 is    4 *    5 slabs with   23 > *   18 grid cells on this image. > Decomposition information on image    2 is    4 *    5 slabs with   23 > *   18 grid cells on this image. > Decomposition information on image    4 is    4 *    5 slabs with   21 > *   18 grid cells on this image. > Decomposition information on image    5 is    4 *    5 slabs with   23 > *   18 grid cells on this image. > Decomposition information on image    3 is    4 *    5 slabs with   23 > *   18 grid cells on this image. > Decomposition information on image    8 is    4 *    5 slabs with   21 > *   18 grid cells on this image. > Decomposition information on image   10 is    4 *    5 slabs with   23 > *   18 grid cells on this image. > Decomposition information on image   19 is    4 *    5 slabs with   23 > *   18 grid cells on this image. > > ... etc. (see http://moene.org/~toon/random-weather.f90). > > I presume other Linux distributors will follow shortly (this *is* > Debian Testing, which can be a bit testy at times - but I do trust my > main business at home on it for over 15 years now). > > Kind regards, > Thanks, good to see it being tested (I'm the Debian/Ubuntu packager). caf /cafrun has been dropped (for the moment ? ) in favour of mpirun, but I've added pkg-config caf packages so that becomes an option. $ pkg-config caf-mpich --libs -L/usr/lib/x86_64-linux-gnu/open-coarrays/mpich/lib -lcaf_mpich -Wl,-z,relro -lmpich -lm -lbacktrace -lpthread -lrt (My thinking is that for libraries in particular, the user need not know whether CAF is being used, and if lib foobar uses CAF, then adding a:     Requires: caf into the pkg-config file gives you the correct linking transparently. The "strange" paths are due to Debians multiarch : it is possible to include libraries for multiple architectures simultaneously. This works ok with pkg-config and cmake , etc (which allow you to set PKG_CONFIG_PATH and have multiple pkgconfig files for different libs simultaneously) , but currently break wrappers such as caf / cafrun. I can add a new package for caf / cafrun but would rather not. (W e currently don't do non-MPI CAF builds). There is currently pkg-config files 'caf-mpich' and 'caf-openmpi' for testing, and I'm adding a default alias caf -> caf-$(default-MPI) regards Alastair -- Alastair McKinstry, , , https://diaspora.sceal.ie/u/amckinstry Misentropy: doubting that the Universe is becoming more disordered.