From: Dan Nagle <danlnagle@me.com>
To: GCC-Fortran-ML <fortran@gcc.gnu.org>,
GCC-Patches-ML <gcc-patches@gcc.gnu.org>
Subject: Re: [Fortran, Patch] First patch for coarray FAILED IMAGES (TS 18508)
Date: Mon, 08 Aug 2016 17:12:00 -0000 [thread overview]
Message-ID: <FD3D1BAE-7EEE-4598-9570-60EDB2AD42F9@me.com> (raw)
In-Reply-To: <CAHqFgjXmRHhXPJewu-Nawo4gNtpp_TyYP6vfN2cBPK9_aWreZQ@mail.gmail.com>
Hi,
The failed images features of gfortran are exciting,
and folks here would like to start testing with their scientific codes.
I’d like to build a new gfortran to support them,
but I must build from a trusted source,
which means from trunk, without custom patches.
Can Alessandro’s patch get a review?
Many thanks!
> On Jun 21, 2016, at 10:59, Alessandro Fanfarillo <fanfarillo.gcc@gmail.com> wrote:
>
> * PING *
>
> 2016-06-06 15:05 GMT-06:00 Alessandro Fanfarillo <fanfarillo.gcc@gmail.com>:
>> Dear all,
>>
>> please find in attachment the first patch (of n) for the FAILED IMAGES
>> capability defined in the coarray TS 18508.
>> The patch adds support for three new intrinsic functions defined in
>> the TS for simulating a failure (fail image), checking an image status
>> (image_status) and getting the list of failed images (failed_images).
>> The patch has been built and regtested on x86_64-pc-linux-gnu.
>>
>> Ok for trunk?
>>
>> Alessandro
--
Cheers!
Dan Nagle
prev parent reply other threads:[~2016-08-08 17:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-06 21:05 Alessandro Fanfarillo
2016-06-21 16:59 ` Alessandro Fanfarillo
2016-07-04 22:46 ` Alessandro Fanfarillo
2016-07-15 17:34 ` Alessandro Fanfarillo
2016-07-19 18:56 ` Mikael Morin
2016-07-20 9:39 ` Andre Vehreschild
2016-07-20 19:18 ` Mikael Morin
2016-07-21 19:05 ` Alessandro Fanfarillo
2016-08-04 3:09 ` Alessandro Fanfarillo
2016-08-09 11:23 ` Paul Richard Thomas
2016-08-09 17:44 ` Alessandro Fanfarillo
2016-09-07 21:04 ` Alessandro Fanfarillo
[not found] ` <CAHqFgjXbwQQnnZp5N+WtWnxNxWducGcU9QSdHRhCdPwNf1tdBQ@mail.gmail.com>
2016-09-19 15:58 ` Andre Vehreschild
2016-09-21 18:37 ` Alessandro Fanfarillo
2016-09-28 13:52 ` Alessandro Fanfarillo
2016-08-08 17:12 ` Dan Nagle [this message]
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=FD3D1BAE-7EEE-4598-9570-60EDB2AD42F9@me.com \
--to=danlnagle@me.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
/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).