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

GFortran 10 Argument Mismatch #206

Open
ax3l opened this issue May 11, 2020 · 2 comments
Open

GFortran 10 Argument Mismatch #206

ax3l opened this issue May 11, 2020 · 2 comments

Comments

@ax3l
Copy link
Contributor

ax3l commented May 11, 2020

Just as in ADIOS2: ornladios/ADIOS2#2228

@michaelkuhn reported an issue in Spack, which indicated that ADIOS needs the Fortran compiler flag -fallow-argument-mismatch flag in order to build with GCC/GFortran 10.

Note:

Using this option is strongly discouraged. It is possible to provide standard-conforming code which allows different types of arguments by using an explicit interface and TYPE(*). 

https://gcc.gnu.org/onlinedocs/gfortran/Fortran-Dialect-Options.html

Describe the bug
Please see spack/spack#16569

To Reproduce
s. above

Desktop (please complete the following information):

  • OS/Platform: Ubuntu
  • Build: GCC 10
  • ADIOS version: 1.13.1

Additional context
See: spack/spack#16569

@NAThompson
Copy link

NAThompson commented Aug 3, 2020

Yeah, I just hit this as well; I couldn't figure out a robust fix. My workaround was just

FCFLAGS="-g -O2 -fallow-argument-mismatch" ./configure

which I suppose is fairly obvious to anyone who works with configure scripts with any regularity. (Not me!)

@ax3l
Copy link
Contributor Author

ax3l commented Aug 24, 2020

Yes, We were wondering if there is an actual change that we can implement in the code to address the raised diagnostics instead of muting it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants