Whoops, hi Damian,
sorry for my late reply. I just saw your mail. I am still hanging ~2000
Fortran-Mailinglist mails back and because you copied the mailing list, your
mail got filtered to the mailing list folder and I didn't see it in the vast
number or unread mails.
> Thanks for your latest
Hi Andre,
Thanks for your latest work on CAF features. Could you let us know whether
this commit should be tested against the OpenCoarrays master branch or another
branch? With the master branch, I get one test failure (not counting two known
teams failures that are actually false negatives
Hi all,
no objections received therefore committed as r257813. Thanks for fast review
Jerry.
- Andre
On Sun, 18 Feb 2018 18:33:07 +0100
Andre Vehreschild wrote:
> Well, after discussing on IRC whether RM should be bothered, I was asked to
> simplify release managers lives and
Well, after discussing on IRC whether RM should be bothered, I was asked to
simplify release managers lives and propose, that if no one objects within one
day, I will merge the patch. So any objections?
- Andre
On Sun, 18 Feb 2018 18:07:28 +0100
Andre Vehreschild wrote:
> Dear
Dear release managers,
this patch (for reference https://gcc.gnu.org/ml/fortran/2018-02/msg00124.html)
fixes a regression in the coarray api by extending three relatively new
functions with one or two arguments, respectively. The patch has been approved
by gfortran devs. Asking your approval to
On 02/18/2018 07:39 AM, Andre Vehreschild wrote:
Hi all,
attached patch fixes an issue with the coarray API. When a component of a
derived type coarray was referenced using a caf_*_by_ref () function and that
component was not an array with a descriptor, then the type of the component was
not
Hi all,
attached patch fixes an issue with the coarray API. When a component of a
derived type coarray was referenced using a caf_*_by_ref () function and that
component was not an array with a descriptor, then the type of the component was
not known. Which additionally meant, that type