[PATCH] Character length cleanup for Coarray Fortran library

Zaak Beekman zbeekman@gmail.com
Sat Feb 10 19:25:00 GMT 2018


>
> Janne, I've scanned the patch and it appears to a
> fairly straight foward mechanical s/int/size_t
> (and similar for nodes).  OK to commit (although
> you may want to wait for a response from Damain
> or Izaak Beekman).
>
> As this breaks an ABI and we've broken it for 8.0,
> I think this should go into trunk.  You may need
> to ping Jakub or Richard for final approval.
>
> --
> Steve
>

Hi Janne & Steve,

I'm still getting used to the GFortran mailing list, and trying to get up
to speed with your dev practices, so please bear with me.

Also, let me add the caveat that, to date, I have mostly dealt with the
OpenCoarrays build system and various project
management/documentation/QA/CI and other administrivia and devops related
stuff---I am not *super* intimately familiar with the actual code base and
ABI. I am even less familiar with the GFortran inner workings. Alessandro
Fanfarillo and Andre are certainly more knowledgeable than I am in this
area.

Is my understanding correct that I can just look at changes to caf_single.c
and the header files to determine where the type changes will impact
OpenCoarrays? A concise list of ABIs/APIs that need changes on the
OpenCoarrays side would go a long way in helping us/me make the
corresponding changes on the OpenCoarrays side. Also, this patch will only
be merged into trunk, right? I.e., it will impact GFortran 8+, and not
future releases on the 6 and 7 branches?

Thanks,
Zaak

Izaak "Zaak" Beekman

-------------------------------------------------------------------------------

HPC Scientist
ParaTools Inc. <http://www.paratools.com/>
5520 Research Park Drive
Suite 100
Baltimore, MD 21228
phone: (443) 543-5475
mobile: (917) 797-3239
-------------------------------------------------------------------------------



More information about the Fortran mailing list