[petsc-dev] changes for petsc tests for XL Fortran compiler

[Smith, Barry F.]

> On Jun 13, 2018, at 6:26 AM, Balay, Satish <balay at mcs.anl.gov> wrote:
> 
> Thanks for the fixes. I have slightly different fixes for these issues in balay/fix-ibm-xl-compilers/maint
> 
> https://bitbucket.org/petsc/petsc/commits/79350f802fe4767769942d977a87579d4a8ad6a0
> 
> [will get merged to next for regular testing - and then to maint]
> 
> Let me know if there are any outstanding problems with it with XL compilers.
> 
> Barry, I've changed
> 
> -#define PetscFlush(a)    call flush_(a)
> +#define PetscFlush(a)    flush_(a)
> 
> this way the example/user code uses:
> 
> +        call PetscFlush(6)
> 
> [i.e with the 'call' statement explicitly listed in example/user code]

   This is fine (except for possibly one user who would just need to change their code).

    Barry

> 
> Satish
> 
> On Fri, 1 Jun 2018, Smith, Barry F. wrote:
> 
>> 
>>   Serban,
>> 
>>     Thanks for the patches. We'll get fixes into the maint branch and hence the next patch release.
>> 
>>   Satish,
>> 
>>     We have the macro PetscFlush() that should be used for the call flush(6) locations to make the Fortran example code portable. (But needs to be tested since currently it is not used).
>> 
>>    Barry
>> 
>> 
>>> On Jun 1, 2018, at 9:21 AM, Serban Maerean <serban at us.ibm.com> wrote:
>>> 
>>> Hello,
>>> 
>>> FYI, I needed to build PETSc test cases with the XL Fortran compiler and had to make the following changes, in <petsc install directory>/share/petsc/examples/: .
>>> 
>>> The reasons for these changes was to be able to build w/the XL Fortran compiler (and w/out Fortran name mangling, which is the default for the XL Fortran compiler.)
>>> 
>>> Let me know if you have any questions.
>>> 
>>> Thanks,
>>> 
>>> 
>>> Serban Maerean
>>> HPC Tools
>>> T/L: 293-9770, Tel.: 845-433-9770
>>> E-mail: serban at us.ibm.com 
>>> <xlc-test-3.9.0.diff>
>> 
>