https://gcc.gnu.org/bugzilla/show_bug.cgi?id=50392
--- Comment #12 from Steve Kargl <sgk at troutmask dot apl.washington.edu> ---
On Mon, May 15, 2017 at 02:27:04PM +0000, zeccav at gmail dot com wrote:
>
> --- Comment #11 from Vittorio Zecca <zeccav at gmail dot com> ---
> You still around, Steven?
> I cannot say I missed you.
I've never left, and you're more than welcomed to delete
all my patches from your copy of gfortran as you can
obviously to better.
% grep -i kargl gcc/fortran/ChangeLog-2011 | wc -l
15
% grep -i kargl gcc/fortran/ChangeLog-2012 | wc -l
3
% grep -i kargl gcc/fortran/ChangeLog-2013 | wc -l
3
% grep -i kargl gcc/fortran/ChangeLog-2015 | wc -l
62
% grep -i kargl gcc/fortran/ChangeLog-2016 | wc -l
53
% grep -i kargl gcc/fortran/ChangeLog | wc -l
1
% grep -i kargl libgfortran/ChangeLog-2013 | wc -l
1
% grep -i kargl libgfortran/ChangeLog-2014 | wc -l
2
% grep -i kargl libgfortran/ChangeLog-2015 | wc -l
2
% grep -i kargl libgfortran/ChangeLog-2016 | wc -l
1
% grep -i kargl libgfortran/ChangeLog | wc -l
1
I do find posts of the form
> Still in 7.1.0 and in trunk 8.0.0!
> Will it ever be fixed?
to be rather condescending. There is a dwindling number of
gfortran developers, and posts like yours is a contributing
reason.
