Skip to content

Debugging globo warnings

Paolo Davini requested to merge debug-globo into python-jinja

Due to #12, we are trying to ask compilers to provide the full set of errors that are found in the code.

This is done by setting fortran flags to

EDIT (the original configuration is too strict): -g -Wall -Werror -fcheck=all -fbounds-check -fbacktrace -finit-real=zero -fopenmp -ffpe-trap=invalid,zero,overflow -ffpe-summary=invalid,zero,overflow -g -fcheck=all -fbounds-check -fbacktrace -finit-real=zero -fopenmp -ffpe-trap=invalid,zero,overflow -ffpe-summary=invalid,zero,overflow -fallow-argument-mismatch

Since it is much easier to do this investigation with the pyglobo environment, I started from MR !19 (merged), doing this on tintin

For those who want to participate, you need to compile in debug mode

./pyglobo-tool.py tintin --globo --clean --debug

To compile and launch a test run (MANDATORY AFTER ANY MODIFICATION)

./pyglobo-tool.py tintin --globo --clean --sbatch TEST

Please note that if you have never compiled globo before, you should run

./pyglobo-tool.py tintin --all --clean

Edited by Paolo Davini

Merge request reports