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

build errors on GCC 10 (gfortran) #73

Open
dpgarrick opened this issue Aug 29, 2022 · 2 comments · May be fixed by #77
Open

build errors on GCC 10 (gfortran) #73

dpgarrick opened this issue Aug 29, 2022 · 2 comments · May be fixed by #77

Comments

@dpgarrick
Copy link

GCC10 is the default on Ubuntu 22.04.

During the build step there are many compilation errors of the form:

scalapack/SRC/pstrord.f:3264:54:

  490 |      $         CALL IGAMX2D( ICTXT, 'All', TOP, 1, 1, MMAX, 1, -1,
      |                                                      2
......
 3264 |                CALL IGAMX2D( ICTXT, 'All', TOP, 1, 1, INFO, 1, -1,
      |                                                      1
Error: Rank mismatch between actual argument at (1) and actual argument at (2) (rank-1 and scalar)

See this link for the explanation and the fix.
https://gcc.gnu.org/gcc-10/porting_to.html

Until the code is fixed the workaround is to configure cmake with the following flag: -DCMAKE_Fortran_FLAGS="-fallow-argument-mismatch" which converts the error into a warning.

e.g.

mkdir -p build && cd build && cmake -DCMAKE_Fortran_FLAGS="-fallow-argument-mismatch" .. && make scalapack

@weslleyspereira
Copy link
Collaborator

Thanks for the observation and for the workaround!

Just to repeat what is in your link: GCC 10 now rejects argument mismatches occurring in the same source file.

@scivision scivision linked a pull request Nov 22, 2022 that will close this issue
@torehl
Copy link

torehl commented May 25, 2023

Same issue on gcc-11.3.0. Thanks for workaround.

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

Successfully merging a pull request may close this issue.

3 participants