Re: [PATCH 9/13] Coarray shared memory library
Jerry D <[email protected]>
| Newsgroups | gmane.comp.gcc.patches,gmane.comp.gcc.fortran |
|---|---|
| Message-ID | <[email protected]> |
On 2/11/26 12:24 PM, Sandra Loosemore wrote:
> On 2/10/26 11:20, Jerry D wrote:
>> Dear all, as requested,
>>
>> See attached patch 9 of 13
>
> More documentation comments:
>
>> diff --git a/gcc/fortran/invoke.texi b/gcc/fortran/invoke.texi
>> index 6e8e13a982b..c544037033a 100644
>> --- a/gcc/fortran/invoke.texi
>> +++ b/gcc/fortran/invoke.texi
>> @@ -2350,6 +2350,15 @@ memory.
>>
>> Warning: Choosing a large shared memory size may produce large coredumps!
>>
>> +@env{GFORTRAN_IMAGE_RESTARTS_LIMIT}: On certain platforms, esp. MacOS, the
>> +shared memory segment needs to be placed on the same (virtual) address in every
>> +image or synchronisation primitives do not work as expected. Unfortunately are
>
> Please use American spelling, e.g. synchronization.
>
>> +some OSes somewhat arbitrary on when they can do this. When the OS is not able
>
> s/are some OSes/some operating systems are/
>
>> +to fullfill the request, then the image aborts itsself and is restarted by the
>
> s/fullfill/fulfill/
> s/itsself/itself
>
>> +supervisor untill the OS complies. This environment variable limits the total
>
> s/untill/until/
>
>> +number of restarts of all images having an issue with shared memory segment
>> +placement. The default value is 4000.
>> +
>> The shared memory coarray library internally uses some additional environment
>> variables, which will be overwritten without notice or may result in failure to
>> start. These are: @code{GFORTRAN_IMAGE_NUM}, @code{GFORTRAN_SHMEM_PID} and
>
> -Sandra
Duly noted and thanks for comments.
I will update.
Jerry