Re: Coarrays in Debian Testing.

[Zaak Beekman <zbeekman@gmail.com>]

Hi Toon et al.,

FYI, I'm not sure how up-to-date thos debian packages are. We have worked
with the Debian package maintainer in the past but I'm not sure if they
regularly create .debs for our releases through an automated system, or if
someone needs to manually update the .debs.

I would be curious to know: 1) which version they have (try running `caf
--version` assuming they package the caf wrapper script) and 2) how you
make out running it.

Most tests that Jerry pointed to you are in the form of stand alone fortran
programs that will print "Test passed." if there are no test failures. Stay
away from the integration tests because those are more complicated to
build.
https://github.com/sourceryinstitute/OpenCoarrays/tree/master/src/tests/unit is
the best place to start and
https://github.com/sourceryinstitute/OpenCoarrays/tree/master/src/tests/regression/reported
but
be aware that some tests require certain MPI features and some tests are
only compatible with GFortran >= 7 or GFortran >= 8. (e.g., failed images
needs experimental MPIX routines only implemented in MPICH  >= 3.2 and even
then, there is an MPICH bug that Andre fixed which was merged with master
but is not in any release yet that can cause some other tests to fail.)

There is also an effort started to get an RPM package into fedora. Anyone
who wants to take a look or offer advice should check out
https://bugzilla.redhat.com/show_bug.cgi?id=1560874

Best,
Zaak



On Fri, Mar 30, 2018 at 8:45 PM <fortran-digest-help@gcc.gnu.org> wrote:

>
> fortran Digest 31 Mar 2018 00:44:45 -0000 Issue 4644
>
> Topics (messages 50150 through 50154):
>
> Re: [patch, fortran] Fix PR 85111, some more zero size stuff
>         50150 by: Jerry DeLisle
>
> [patch, fortran, testsuite, committed] Remove illegal code from
> substr_6.f90
>         50151 by: Thomas Koenig
>
> Coarrays in Debian Testing.
>         50152 by: Toon Moene
>         50153 by: Jerry DeLisle
>
> Patching the GCC build system to build MPICH and OpenCoarrays
>         50154 by: Damian Rouson
>
> Administrivia:
>
> To subscribe to the digest, e-mail:
>         fortran-digest-subscribe@gcc.gnu.org
>
> To unsubscribe from the digest, e-mail:
>         fortran-digest-unsubscribe@gcc.gnu.org
>
> To post to the list, e-mail:
>         fortran@gcc.gnu.org
>
>
> ----------------------------------------------------------------------
>
>
>
> ---------- Forwarded message ----------
> From: Jerry DeLisle <jvdelisle@charter.net>
> To: Thomas Koenig <tkoenig@netcologne.de>, "fortran@gcc.gnu.org" <
> fortran@gcc.gnu.org>, gcc-patches <gcc-patches@gcc.gnu.org>
> Cc:
> Bcc:
> Date: Thu, 29 Mar 2018 19:30:47 -0700
> Subject: Re: [patch, fortran] Fix PR 85111, some more zero size stuff
> On 03/29/2018 11:07 AM, Thomas Koenig wrote:
> > Hello world,
> >
> > the attached patch fixes PR 85111, a regression introduced with my
> > recent simplification patches.  Seems like the zero-size saga
> > has yet another chapter :-)
> >
> > Regression-tested. OK for trunk?
> >
>
> Looks OK,
>
> Thanks,
>
> Jerry
> > Regards
> >
> >      Thomas
> >
> > 2017-03-29  Thomas Koenig  <tkoenig@gcc.gnu.org>
> >
> >          PR fortran/85111
> >          * array.c (gfc_resolve_character_array_constructor): Early
> >          exit for zero-size arrays.
> >          * simplify.c (simplify_transformation_to_array): Exit early
> >          if the result size is zero.
> >          (simplify_minmaxloc_to_array): Likewise.
> >
> > 2017-03-29  Thomas Koenig  <tkoenig@gcc.gnu.org>
> >
> >          PR fortran/85111
> >          * gfortran.dg/zero_sized_10.f90: New test.
>
>
>
>
> ---------- Forwarded message ----------
> From: Thomas Koenig <tkoenig@netcologne.de>
> To: "fortran@gcc.gnu.org" <fortran@gcc.gnu.org>, gcc-patches <
> gcc-patches@gcc.gnu.org>
> Cc:
> Bcc:
> Date: Fri, 30 Mar 2018 14:18:42 +0200
> Subject: [patch, fortran, testsuite, committed] Remove illegal code from
> substr_6.f90
> Hello world,
>
> F2003, 6.1.1. "Substrings" states that
>
> Both the starting point and the ending
> point shall be within the range 1, 2, ..., n unless the starting point
> exceeds the ending point, in which
> case the substring has length zero.
>
> The attached patch, which corrects the test case, has
> been committed as obvious.
>
> What's left is the accepts-invalid bug.
>
> Regards
>
>         Thomas
>
> 2018-03-30  Thomas Koenig  <tkoenig@gcc.gnu.org>
>
>         PR fortran/85130
>         * gfortran.dg/substr_6.f90: Remove illegal test for
>         out-of-bounds substring.
>
>
>
> ---------- Forwarded message ----------
> From: Toon Moene <toon@moene.org>
> To: gfortran <fortran@gcc.gnu.org>
> Cc:
> Bcc:
> Date: Fri, 30 Mar 2018 16:19:29 +0200
> Subject: Coarrays in Debian Testing.
> I just noticed that the following packages were available in Debian
> Testing:
>
> libcaf-mpi2 - Co-Array Fortran libraries for gfortran
> libcoarrays-dev - Co-Array Fortran libraries for gfortran - development
> files
> open-coarrays-bin - Executables for running Co-Array Fortran programs
>
> so I installed them.
>
> Are there any test programs to test this Debian installation (before I
> am going proclaim them "useful" ?)
>
> Thanks in advance,
>
> --
> Toon Moene - e-mail: toon@moene.org - phone: +31 346 214290
> <+31%20346%20214%20290>
> Saturnushof 14, 3738 XG  Maartensdijk, The Netherlands
> At home: http://moene.org/~toon/; weather: http://moene.org/~hirlam/
> Progress of GNU Fortran: http://gcc.gnu.org/wiki/GFortran#news
>
>
>
> ---------- Forwarded message ----------
> From: Jerry DeLisle <jvdelisle@charter.net>
> To: Toon Moene <toon@moene.org>, gfortran <fortran@gcc.gnu.org>
> Cc:
> Bcc:
> Date: Fri, 30 Mar 2018 10:03:32 -0700
> Subject: Re: Coarrays in Debian Testing.
> On 03/30/2018 07:19 AM, Toon Moene wrote:
> > I just noticed that the following packages were available in Debian
> > Testing:
> >
> > libcaf-mpi2 - Co-Array Fortran libraries for gfortran
> > libcoarrays-dev - Co-Array Fortran libraries for gfortran - development
> > files
> > open-coarrays-bin - Executables for running Co-Array Fortran programs
> >
> > so I installed them.
> >
> > Are there any test programs to test this Debian installation (before I
> > am going proclaim them "useful" ?)
> >
> > Thanks in advance,
> >
>
> Go here and look in these test directories:
>
> https://github.com/sourceryinstitute/OpenCoarrays/tree/master/src/tests
>
> There are examples of pde solvers etc.
>
> Jerry
>
>
>
> ---------- Forwarded message ----------
> From: Damian Rouson <damian@sourceryinstitute.org>
> To: GCC Development <gcc@gcc.gnu.org>, gfortran <fortran@gcc.gnu.org>
> Cc: Daniel Celis Garza <daniel.celisgarza@hmc.ox.ac.uk>, Jerry DeLisle <
> jvdelisle@charter.net>, "Filippone, Salvatore" <
> salvatore.filippone@cranfield.ac.uk>
> Bcc:
> Date: Fri, 30 Mar 2018 17:44:37 -0700
> Subject: Patching the GCC build system to build MPICH and OpenCoarrays
> All,
>
> Jerry DeLisle, Daniel Celis Garza, and I would greatly appreciate feedback
> on our approach to patching the GCC build system to build MPICH and
> OpenCoarrays after it builds gfortran (gfortran requires MPI and
> OpenCoarrays to support the parallel features of Fortran 2008 and Fortran
> 2018).  A diff of our work relative to the GCC trunk is at
> http://bit.ly/2pQuzvS.  Our steps so far include the following:
>
> 1. Jerry wrote an autotools build system for OpenCoarrays (on the
> OpenCoarrays issue-343-gnu-build branch.)
> 2. Jerry got MPICH and OpenCoarrays tar balls onto the GCC ftp server.
> 3. I modified GCC’s contrib/download_prerequisites script to download the
> tar balls.
> 4. Daniel edited GCC’s Makefile.def, config.ac, and Makefile.tpl to
> incorporate MPICH.
>
> Our current issue is that the Makefile produced as follows doesn’t create
> the desired “mpi" directory:
>
> git clone -b build-mpich https://github.com/sourceryinstitute/gcc
> mkdir -p gcc/build
> cd gcc/build
> ../configure --disable-bootstrap --enable-languages=fortran
>
> whereupon "grep mpi Makefile” only returns comments and an echo
> statement.  Ultimately, our desired sequence is to build gfortran, then
> build MPICH, and then build OpenCoarrays.  All advice is welcome.
>
> Damian
>
>
>
>
>
>
>
>