public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Damian Rouson <damian@sourceryinstitute.org>
To: Janne Blomqvist <blomqvist.janne@gmail.com>
Cc: "Fortran List" <fortran@gcc.gnu.org>,
	"GCC Patches" <gcc-patches@gcc.gnu.org>,
	"Izaak@izaakbeekman.com" <izaak@izaakbeekman.com>,
	"Alessandro Fanfarillo" <elfanfa@ucar.edu>,
	"Andre Vehreschild" <vehre@gmx.de>
Subject: Re: [PATCH] Character length cleanup for Coarray Fortran library
Date: Wed, 21 Feb 2018 20:19:00 -0000	[thread overview]
Message-ID: <etPan.5a8dd44c.61187cef.8ad@sourceryinstitute.org> (raw)
In-Reply-To: <CAO9iq9HoSZkJ+MuwsxooHeXE-q3DoUGybBGfJzCv9cFj+uAaQg@mail.gmail.com>

 



On February 21, 2018 at 11:35:47 AM, Janne Blomqvist (blomqvist.janne@gmail.com(mailto:blomqvist.janne@gmail.com)) wrote:

> PING  
>  
> Is anybody planning to work on this on the opencoarrays side? Or do  
> you prefer that this is just committed and you can sort it out on your  
> own schedule?  

Hi Janne,

The trunk didn’t build for me the first time I tried soon after your initial email and it took me until yesterday to find time to try again.  Once I succeeded, the patch created three new test failures.  I’m wondering if Andre’s recent patch (r257813) helped reduce the number.  All new failures involve the failed-images features developed by Alessandro and Andre, both of whom now have new employment or contracts that prevent making significant contributions to OpenCoarrays (although I hope that will change and am working with Alessandro’s organization to attempt to get some of his time allocated to gfortran/OpenCoarrays development).

I think the most sustainable path forward is for me to assist any interested gfortran developer in building OpenCoarrays on your local system and running the test suite.  At least that eliminates the reliance on OpenCoarrays developers to run the tests every time a patch impacts OpenCoarrays.  If we can work together on building OpenCoarrays on your system, we can also look together at the requisite changes to see if we can eliminate the failures.

Oxford University Ph.D. student Daniel Garza visit Sourcery Institute March 17 - June 2 to integrate the building of OpenCoarrays into the GCC build system so I hope this will all be easier sooner.

Damian 


  reply	other threads:[~2018-02-21 20:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-09 16:11 Janne Blomqvist
2018-02-09 23:27 ` Steve Kargl
2018-02-10 19:34 ` Damian Rouson
2018-02-10 21:21   ` Janne Blomqvist
2018-02-21 19:35     ` Janne Blomqvist
2018-02-21 20:19       ` Damian Rouson [this message]
2018-02-21 20:56         ` Janne Blomqvist
2018-02-21 20:59           ` Izaak Beekman
2018-02-22  0:36           ` Damian Rouson
2018-02-22  9:46             ` Janne Blomqvist
2018-02-22  9:57               ` Janne Blomqvist

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=etPan.5a8dd44c.61187cef.8ad@sourceryinstitute.org \
    --to=damian@sourceryinstitute.org \
    --cc=blomqvist.janne@gmail.com \
    --cc=elfanfa@ucar.edu \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc-patches@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).