Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fortran build emitting large number of warning with gcc-10 #2411

Open
NAThompson opened this issue Aug 5, 2020 · 2 comments
Open

Fortran build emitting large number of warning with gcc-10 #2411

NAThompson opened this issue Aug 5, 2020 · 2 comments
Labels
api: Fortran Fortran API related area: build Build issues bug duplicate triage: low This issue is a nice-to-have if we can get to it but isn't holding anybody up.

Comments

@NAThompson
Copy link
Contributor

Numerous warnings are being emitted by gcc-10 builds of ADIOS2:

Warning: Rank mismatch between actual argument at (1) and actual argument at (2) (rank-1 and scalar)
[361/912] Building Fortran object bindings/Fortran/CMakeFiles/adios2_fortran.dir/modules/adios2_engine_get_mod.f90.o
contains/adios2_engine_get_deferred_by_name.f90:742:41:
......
Warning: Type mismatch between actual argument at (1) and actual argument at (2) (INTEGER(4)/INTEGER(8)).
contains/adios2_engine_put_deferred.f90:152:54:

These can be silenced by the flag -fallow-argument-mismatch, but more thinking is required to decide if this is a reasonable fix.

@NAThompson NAThompson added the triage: low This issue is a nice-to-have if we can get to it but isn't holding anybody up. label Aug 5, 2020
@chuckatkins chuckatkins added api: Fortran Fortran API related area: build Build issues bug duplicate labels Aug 19, 2020
@chuckatkins
Copy link
Contributor

Numerous warnings are being emitted by gcc-10 builds of ADIOS2:
...
These can be silenced by the flag -fallow-argument-mismatch, but more thinking is required to decide if this is a reasonable fix.

They can't be silenced; the -fallow-argument-mismatch flag simply downgrades them from errors to warnings (see https://gcc.gnu.org/gcc-10/porting_to.html). This is already a known issue, #2228 that was resolved in #2250 by adding the appropriate flag to allow compilation and then in #2407 when the CI images started including gcc10 by suppressing the warning on CDash. We decided then to just accept the warnings.

Should we leave this open as a known issue or close it as duplicate / resolved?

@ghorn
Copy link

ghorn commented Jun 29, 2022

You can silence them by supressing all warnings with -w, so you have to do -fallow-argument-mismatch -w

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api: Fortran Fortran API related area: build Build issues bug duplicate triage: low This issue is a nice-to-have if we can get to it but isn't holding anybody up.
Projects
None yet
Development

No branches or pull requests

3 participants