From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17102 invoked by alias); 4 Apr 2018 11:12:29 -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 17082 invoked by uid 89); 4 Apr 2018 11:12:29 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-6.9 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,GIT_PATCH_1,KAM_SHORT,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=assessing, H*i:sk:etPan.5, love X-Spam-User: qpsmtpd, 2 recipients X-HELO: mail-wr0-f170.google.com Received: from mail-wr0-f170.google.com (HELO mail-wr0-f170.google.com) (209.85.128.170) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 04 Apr 2018 11:12:26 +0000 Received: by mail-wr0-f170.google.com with SMTP id p53so21969299wrc.10; Wed, 04 Apr 2018 04:12:26 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=kQcKLF+VoYSWsrXUkRuN+L7Bk+gZMbBK3HJwFT68vMQ=; b=hvaxEC+iCBGqsmyrZ+dvzUeParSZ9RF9j1RY5/z9KqtGFHD/Kzj1mzlO/2pNAMw4Xo CmKWYPhPMPAKJtrTLbFFvg6SFc+RpmFHe7Yf8zQmCus/EcbtNzLfoqVAbr2yRrkrjBqt Nun/b/G4DRyk3JD++bJEX7ceGjjFPcaeuC0uHDsVVQdCueTavqMhGiuT7L2h49dV4m05 3F+8DpzLvgUPilYdnDlVdclBF0oHlukndg1e3UWcTaHVWKd9V+0oMJspXdSmLYjiz8t6 EsTrKL3k9l6YOKsuznddinDu0/GQit3zPGmfiX/zNO/KtWUiP4rt5jpqm446mYCegeLk 2QPw== X-Gm-Message-State: ALQs6tDnEXCCWDBbLih4J/5aRVI5PQW4O9X4mTDJQxiv/thjCqQ+QklU yfr4aUJmHPIPUomqjMd5waTRh5/vTlu3l82WHyo= X-Google-Smtp-Source: AIpwx48tmYy/khjFC3gpzzlE5X9qBXQ8V8hJCdDjiJFonRqQ5n7jG0+JSoF+3+SHK82Rpsmoi2c1NPQt/gNm3/IBiDk= X-Received: by 2002:a19:181b:: with SMTP id o27-v6mr10448976lfi.132.1522840344435; Wed, 04 Apr 2018 04:12:24 -0700 (PDT) MIME-Version: 1.0 Received: by 10.46.115.14 with HTTP; Wed, 4 Apr 2018 04:12:24 -0700 (PDT) In-Reply-To: References: From: Richard Biener Date: Wed, 04 Apr 2018 11:12:00 -0000 Message-ID: Subject: Re: Patching the GCC build system to build MPICH and OpenCoarrays To: Damian Rouson Cc: GCC Development , Jerry DeLisle , gfortran , "Filippone, Salvatore" , Daniel Celis Garza Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes X-SW-Source: 2018-04/txt/msg00013.txt.bz2 On Wed, Apr 4, 2018 at 8:24 AM, Damian Rouson wrote: > On April 3, 2018 at 1:36:37 AM, Richard Biener (richard.guenther@gmail.co= m) > wrote: > > > You probably only want a new target_module for the MPI library. Note > it's name has to match that of the directory containing the sources > which > as far as I see is 'mpich', not 'libmpi'. > > Thanks! I=E2=80=99ll ask Daniel to respond if he has further questions. > > May I ask again why mpi/opencoarrays should be built together with > gfortran rather than separately? Does gfortran or any of its current > target libraries > link against them? > > Yes, gfortran links to OpenCoarrays via the -fcoarray=3Dlib argument. In that case user programs compiled with -fcoarray=3Dlib are but gfortran or libgfortran itself is not linked against OpenCoarrays? > OpenCoarrays provides the only parallel implementations of gfortran=E2=80= =99s > Coarray ABI (http://bit.ly/Coarray-ABI). Any Fortran program that uses the > large set of parallel features in Fortran 2008 and Fortran 2018 must have > OpenCoarrays installed in order for the code to execute in parallel. I see. So if we consider OpenCoarrays part of the gfortran runtime then it makes sense to build it in-tree... > We have found MPICH to be the most robust option and it has the only > released support for some of the more advanced requirements such as the > Fortran 2018 fault-tolerance features. However, there will be configure > options for using MPI implementations other than MPICH. ... but building an mpi library in-tree might not? I'm still lacking an idea of what it takes to enable coarrays with gfortran since install.texi doesn't talk about this at all, neither in the prereques= ites section nor in a fortran/coarray specific section. In fact the only thing I find is in invoke.texi which says @item -fcoarray=3D@var{} @opindex @code{fcoarray} ... @item @samp{lib} Library-based coarray parallelization; a suitable GNU Fortran coarray library needs to be linked. @end table which suggests linking to the coarray library doesn't happen automatically but the user is supposed to link a suitable library? I'd love to "enable" coarray support for openSUSE but as said I have a hard time assessing what I'd need to do here. Thanks, Richard. > > Damian