public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "aluaces at udc dot es" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/110644] Error in gfc_format_decoder Date: Fri, 20 Oct 2023 15:13:06 +0000 [thread overview] Message-ID: <bug-110644-4-b9VPvJhbOC@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110644-4@http.gcc.gnu.org/bugzilla/> 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
next prev parent reply other threads:[~2023-10-20 15:13 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-07-12 16:04 [Bug fortran/110644] New: " kyle.shores44 at gmail dot com 2023-07-12 17:46 ` [Bug fortran/110644] " kargl at gcc dot gnu.org 2023-10-13 19:41 ` jvdelisle at gcc dot gnu.org 2023-10-16 14:32 ` kyle.shores44 at gmail dot com 2023-10-18 15:56 ` aluaces at udc dot es 2023-10-18 17:03 ` sgk at troutmask dot apl.washington.edu 2023-10-19 8:00 ` aluaces at udc dot es 2023-10-19 15:44 ` sgk at troutmask dot apl.washington.edu 2023-10-19 16:00 ` aluaces at udc dot es 2023-10-19 16:19 ` sgk at troutmask dot apl.washington.edu 2023-10-20 15:13 ` aluaces at udc dot es [this message] 2023-10-20 17:29 ` sgk at troutmask dot apl.washington.edu 2023-10-23 15:16 ` aluaces at udc dot es 2024-03-06 3:40 ` jvdelisle at gcc dot gnu.org 2024-03-08 16:44 ` kyle.shores44 at gmail dot com 2024-03-08 16:56 ` kyle.shores44 at gmail dot com 2024-03-08 17:22 ` sgk at troutmask dot apl.washington.edu 2024-03-08 17:42 ` kyle.shores44 at gmail dot com 2024-03-08 17:42 ` kyle.shores44 at gmail dot com 2024-03-08 19:44 ` sgk at troutmask dot apl.washington.edu 2024-03-08 20:01 ` kyle.shores44 at gmail dot com 2024-03-08 20:32 ` sgk at troutmask dot apl.washington.edu
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-110644-4-b9VPvJhbOC@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).