public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/48776] ICE(segfault) after -std=f95 diagnostic error involving PROCEDURE Date: Sat, 20 Jan 2024 15:50:47 +0000 [thread overview] Message-ID: <bug-48776-4-9sOM9N36be@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-48776-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48776 --- Comment #12 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Mikael Morin <mikael@gcc.gnu.org>: https://gcc.gnu.org/g:6930e1f1055c39bea170c25f694f7301989e5d1d commit r14-8305-g6930e1f1055c39bea170c25f694f7301989e5d1d Author: Mikael Morin <mikael@gcc.gnu.org> Date: Fri Jan 19 18:47:36 2024 +0100 fortran: Restore current interface info on error [PR111291] This change is a followup to the fix for PR48776 (namely r14-3572-gd58150452976c4ca65ddc811fac78ef956fa96b0 AKA fortran: Restore interface to its previous state on error [PR48776]), which cleaned up new changes from interfaces upon error. Unfortunately, there is one case in that fix that is mishandled, visible on unexpected_interface.f90 with valgrind or an asan-instrumented gfortran. when an interface statement is found while parsing an interface body (which is invalid), the current interface is replaced by the one from the new statement, and as parsing continues, new procedures are added to the new interface, which has been rejected and freed, instead of the original one. This change restores the current interface pointer to its previous value on each rejected statement. PR fortran/48776 PR fortran/111291 gcc/fortran/ChangeLog: * parse.cc: Restore current interface to its previous value on error.
prev parent reply other threads:[~2024-01-20 15:50 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-04-26 18:46 [Bug fortran/48776] New: " burnus at gcc dot gnu.org 2013-06-16 13:13 ` [Bug fortran/48776] " dominiq at lps dot ens.fr 2023-08-26 18:29 ` mikael at gcc dot gnu.org 2023-08-26 18:30 ` mikael at gcc dot gnu.org 2023-08-26 19:47 ` mikael at gcc dot gnu.org 2023-08-30 12:20 ` cvs-commit at gcc dot gnu.org 2023-08-30 19:38 ` mikael at gcc dot gnu.org 2023-08-30 19:39 ` mikael at gcc dot gnu.org 2024-01-20 15:50 ` cvs-commit at gcc dot gnu.org [this message]
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-48776-4-9sOM9N36be@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).