[petsc-dev] Type mismatch warnings
Satish Balay
balay at mcs.anl.gov
Fri Aug 19 14:24:35 CDT 2022
There is also -Wno-lto-type-mismatch - but don't know if its for this issue or a different one.
Satish
On Fri, 19 Aug 2022, Blaise Bourdin wrote:
> It prints this warning instead of throwing an error. I should have mentioned that this is on a M1 Mac, since gfortran behaviour and flags is so platform-dependent Blaise
>
>
> On Aug 19, 2022, at 1:51 PM, Satish Balay <balay at mcs.anl.gov> wrote:
>
> Does -fallow-argument-mismatch work?
>
> Satish
>
> On Fri, 19 Aug 2022, Blaise Bourdin wrote:
>
> Hi,
>
> Does anybody know if there is a magic gfortran flag to get rid of type mismatch warnings?
> These pop up when using PetscObjectSetName with two different petsc objects, for instance.
>
> Warning: Type mismatch between actual argument at (1) and actual argument at (2) (TYPE(tdm)/TYPE(tpetscsf)).
>
> Regards,
> Blaise
>
> —
> Tier 1 Canada Research Chair in Mathematical and Computational Aspects of Solid Mechanics
> Professor, Department of Mathematics & Statistics
> Hamilton Hall room 409A, McMaster University
> 1280 Main Street West, Hamilton, Ontario L8S 4K1, Canada
> https://www.math.mcmaster.ca/bourdin | +1 (905) 525 9140 ext. 27243
>
>
>
> —
> Tier 1 Canada Research Chair in Mathematical and Computational Aspects of Solid Mechanics
> Professor, Department of Mathematics & Statistics
> Hamilton Hall room 409A, McMaster University
> 1280 Main Street West, Hamilton, Ontario L8S 4K1, Canada
> https://www.math.mcmaster.ca/bourdin | +1 (905) 525 9140 ext. 27243
>
>
>
More information about the petsc-dev
mailing list