compiler errors with AMR/SAAMG enabled

compiler_errors.txt

CC: @gsell

added AMR Bug labels

created merge request !415 (merged) to address this issue

mentioned in merge request !415 (merged)

@frey_m tool-chain (macOS!):

• clang 11
• Open MPI 3.1.6
• HDF5 1.10.6
• OpenBLAS 0.3.20
• parmetes 4.0.3
• AMReX 18.7
• Boot 1.73.0
• Trilions 12.18.1

@gsell Could you maybe check again? The number of errors should now be drastically reduced.

changed title from compiler errors with AMR enabled to compiler errors with AMR/SAAMG enabled

@frey_m @gsell: I am still a bit lost on this. Is this only on Mac, or with certain compilers and versions? Can some more info be added?

No, this issue is not restricted to Mac. I compile on Merlin6 with gcc/9.3.0 getting the same compile error.

A warning -Waggressive-loop-optimizations is thrown due to Trilinos/12.18.1. Since we force -Werror in OPAL, we get a compile error. The warning disappears when we reduce the optimization level from -O3 to -O2.

When I compile OPAL with Trilinos/12.14.1 and gcc/7.3.0, I have not experienced this issue. Since I assume that gcc/7.3.0 would also catch this warning, I think, this issue was introduced in a later version of Trilinos.

okay thanks

With gcc/8.4.0 and trilinos/12.18.1 I don't get a compiler error on merlin.

Ok, thanks for checking.

If I try to compile with ENABLE_IPPL_TESTS=ON I got more aggressive loop optimisation errors. Maybe the best solution is to disable this optimisation with -fno-aggressive-loop-optimizations global. This way we do not loose the other optimisations.

@gsell Ok. I'll undo the #pragma changes and apply -fno-aggressive-loop-optimizations instead.

mentioned in commit 37dbf273

created merge request !421 (merged) to address this issue

mentioned in merge request !421 (merged)

changed milestone to %OPAL 2.4.0

mentioned in commit 37da44f0

closed via merge request !421 (merged)