https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110644

--- Comment #10 from Alberto Luaces <aluaces at udc dot es> ---
Ok, indeed they were some warnings.  I had to use &gfc_current_locus, as you
suggested, so now all of them are pointed at the end of the file.

Yes, I am using OOP: we have a "states" class that has its assignment and copy
methods.  Those are the ones that I think that they are called implicitly by
the compiler, and gfortran is struggling to point exactly where.

I think now I may be able to get a minimal case for aiding solving this bug. 
Let me see if I can.

[4/126] Building Fortran object
CMakeFiles/MBSLIM.dir/solidos/solidos_Sensib.f90.o
[...]solidos/solidos_Sensib.f90:1001:28:

 1001 | END SUBMODULE SOLIDOS_Sensib
      |                            1
Warning: Non-RECURSIVE procedure ‘statescopystates’ at (1) is possibly calling
itself recursively.  Declare it RECURSIVE or use ‘-frecursive’
[...]solidos/solidos_Sensib.f90:1001:28:

 1001 | END SUBMODULE SOLIDOS_Sensib
      |                            1
Warning: Non-RECURSIVE procedure ‘statesassignstates’ at (1) is possibly
calling itself recursively.  Declare it RECURSIVE or use ‘-frecursive’
[...]solidos/solidos_Sensib.f90:1001:28:

 1001 | END SUBMODULE SOLIDOS_Sensib
      |                            1
Warning: Non-RECURSIVE procedure ‘statecopystate’ at (1) is possibly calling
itself recursively.  Declare it RECURSIVE or use ‘-frecursive’
[...]solidos/solidos_Sensib.f90:1001:28:

 1001 | END SUBMODULE SOLIDOS_Sensib
      |                            1
Warning: Non-RECURSIVE procedure ‘stateassignstate’ at (1) is possibly calling
itself recursively.  Declare it RECURSIVE or use ‘-frecursive

Reply via email to