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: Thu, 19 Oct 2023 16:00:10 +0000 [thread overview] Message-ID: <bug-110644-4-NRzVamkDuK@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 #8 from Alberto Luaces <aluaces at udc dot es> --- No, I meant building *gcc* with those flags, but alas each gcc compilation stage was still building with "-O2" so almost all of the compiler structures are still optimized. Nevertheless I did what you suggest and climbed up those 6 levels to find that indeed expr->where has null fields. To me it is not very strange since in my code there is a structure that has copy and assignment members. gfortran is arguing about them being called in another module, but of course there is no physical place where they are called, as this is done implicitly by the compiler when using those kind of objects, if I am correct. I am rebuilding with your suggested gfc_current_locus change and reporting the results.
next prev parent reply other threads:[~2023-10-19 16:00 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 [this message] 2023-10-19 16:19 ` sgk at troutmask dot apl.washington.edu 2023-10-20 15:13 ` aluaces at udc dot es 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-NRzVamkDuK@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).