public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jerry DeLisle <jvdelisle@charter.net>
To: FX <fxcoudert@gmail.com>
Cc: gfortran <fortran@gcc.gnu.org>, GCC Development <gcc@gcc.gnu.org>,
	Damian Rouson <damian@sourceryinstitute.org>,
	Izaak Beekman <izaak@izaakbeekman.com>,
	Andre Vehreschild <vehre@gmx.de>
Subject: Re: [patch, libgfortran RFC] Installation script for OpenCoarrays to enable multi-image gfortran
Date: Thu, 26 Jan 2017 16:12:00 -0000	[thread overview]
Message-ID: <2047e9a6-6d7a-1aae-3c2d-4ad1b9c25e88@charter.net> (raw)
In-Reply-To: <3FD52C1D-E46B-4ADD-AEF1-DB2AD659F0C5@gmail.com>

On 01/26/2017 05:25 AM, FX wrote:
> Hi Jerry,
> 
> A few questions:
> 
>   - why mpich? doesn’t opencoarrays support any MPI implementation?

We picked it as one that I had available and only as a starting point, we plan
to add support for other libraries as we go. (OpenCoarrays itself does support
other libraries)

>   - I am a bit surprised by the complexity of the script… couldn’t we provide a Makefile for opencoarrays, to be compatible with our other build requirements?

I agree, this script is using Boiler Plate which allows a lot of flexibility and
provides some diagnostics and handling of script errors. It builds on things the
OpenCoarrays team is familiar with and was the quickest way to go initially. My
first draft script was about 50 lines with comments, but it had no error checks.
I will be able to reduce what you see when I narrow down to one tracked release
package.

>   - do we want to work towards seamless implementation of coarrays into gfortran, or coexistence as a separate package (as is currently the case, for example in Mac Homebrew, where it ships as a separate — but compatible — package)?

I think we do want to head toward seamless. I have explored even copying the
source directly into the caf directory of libgfortran and merging the .h files,
but this takes some time to do and would leave two sets of sources to maintain.
Regarding things like Homebrew, or rpm packages, it will require us to learn how
to do these packages which none of us know right now.

Ultimately, since multi images is part of the Fortran language, it should just
happen transparently with the gcc regular build process.

Jerry

  reply	other threads:[~2017-01-26 16:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-25 19:37 Jerry DeLisle
2017-01-26 13:25 ` FX
2017-01-26 16:12   ` Jerry DeLisle [this message]
2017-01-28  2:13     ` Damian Rouson
2017-01-28 11:22       ` FX
2017-01-28 17:23         ` Jerry DeLisle
2017-01-28 17:56           ` FX
     [not found]             ` <773757770.55906.1485810049667@mail.yahoo.com>
2017-01-31  8:11               ` FX
     [not found]                 ` <CAE0_W2VWPN6nxO0eHbRibgT7fu9fwnWAVD_2b_5uxFDpzFAzHg@mail.gmail.com>
2017-01-31 16:36                   ` FX
     [not found]         ` <CAAbnBwaL1m+smdtPsNdoY6u2cyYUbm97qYZBjikL=9GqX3hh-Q@mail.gmail.com>
2017-01-28 18:04           ` FX
2019-02-05 22:08       ` Gfortran GSoC (Was: Re: [patch, libgfortran RFC] Installation script for OpenCoarrays to enable multi-image gfortran) Martin Jambor

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2047e9a6-6d7a-1aae-3c2d-4ad1b9c25e88@charter.net \
    --to=jvdelisle@charter.net \
    --cc=damian@sourceryinstitute.org \
    --cc=fortran@gcc.gnu.org \
    --cc=fxcoudert@gmail.com \
    --cc=gcc@gcc.gnu.org \
    --cc=izaak@izaakbeekman.com \
    --cc=vehre@gmx.de \
    /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.
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).