gfortran needs new contributors.

[Arjen Markus]

Hi Steve,

this seems fairly easy to do, given that the solution is already there.

I am willing to give it a try.

Regards,

Arjen

Op zo 21 jun. 2020 om 06:44 schreef Steve Kargl via Fortran
<fortran@gcc.gnu.org>:
>
> There are currently 1002 open bug reports for gfortran.
>
> gfortran development is in need of new contributors.
> To help individuals with little or no experience with
> the gfortran source code to get involved, the following
> gfortran bug reports (https://gcc.gnu.org/bugzilla) have
> patches posted to their audit trails:
>
> 30372 (5 patches, last 5 comments)  93635 95038 95340
> 95342 95352 95372 95446 95501 95502 95543 95584 95585
> 95586 95612 95613 95614 95647 95708 95709 95710
>
> The patches have been tested against the code posted
> in the bug reports.  That code has not been converted
> to suitable code for the gfortran testsuite.  Thus,
> an individual interest in getting involved with gfortran
> development will need to convert the code for the
> testsuite (help will be given if asked for).  Additionally,
> the patches have not goen through regression testing.
>
> Here is a chance for gfortran users to become contributors.
> I'm willing to explain what I know about gfortran internals
> to help with the above listed patches.
>
> --
> Steve