This is the mail archive of the
mailing list for the GCC project.
Re: [patch, libgfortran RFC] Installation script for OpenCoarrays to enable multi-image gfortran
- From: FX <fxcoudert at gmail dot com>
- To: Damian Rouson <damian at rouson dot net>
- Cc: Jerry DeLisle <jvdelisle at charter dot net>, Damian Rouson <damian at sourceryinstitute dot org>, Izaak Beekman <izaak at izaakbeekman dot com>, Andre Vehreschild <vehre at gmx dot de>, gfortran <fortran at gcc dot gnu dot org>, GCC Development <gcc at gcc dot gnu dot org>
- Date: Sat, 28 Jan 2017 12:22:10 +0100
- Subject: Re: [patch, libgfortran RFC] Installation script for OpenCoarrays to enable multi-image gfortran
- Authentication-results: sourceware.org; auth=none
- References: <email@example.com> <3FD52C1D-E46B-4ADD-AEF1-DB2AD659F0C5@gmail.com> <firstname.lastname@example.org> <CAE0_W2Xi5G239C3zoWo+TNMiOibJR=dBMLYSj5c+q+u+yVk_pg@mail.gmail.com>
> It would be difficult or impossible for several OpenCoarrays
> developers to contribute without OpenCoarrays remaining separate for
> several reasons.
No, I understand that. What I meant is: do want to provide seamless integration, so that libgfortran builds would automatically detect if an MPI environment is available, and if so build opencoarrays. The only “hard" dependency is whether we have an mpicc, it seems.
However, the big issue is that of build-time requirements, which are not compatible with GCC: opencoarrays depends on cmake and bash, so it is in that respect very different from GMP and MPFR, which do not have stricter requirement than GCC itself.
I’ve started today to look at the OpenCoarrays source, and I admit I am quite lost… it seems that the build machinery is much larger than the source itself. Technically, it seems doable to OpenCoarrays a “Makefile.gfortran” that would build OpenCoarrays, without the need for bash or cmake. Does this sound right to you?
>> Ultimately, since multi images is part of the Fortran language, it should just
>> happen transparently with the gcc regular build process.
> We’re all in agreement here so hopefully Jerry’s submission will be
Currently, I don’t think we can integrate it in this form, due to build requirements. Maybe the threshold is lower for integrating it into GCC’s contrib scripts directory?