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/67804] ICE on data initialization of type(character) with wrong data Date: Sun, 16 Jan 2022 20:40:56 +0000 [thread overview] Message-ID: <bug-67804-4-7gTaNtVqa9@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-67804-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67804 --- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-11 branch has been updated by Harald Anlauf <anlauf@gcc.gnu.org>: https://gcc.gnu.org/g:c5bf6dc27cdb091f1f8046f98ce7ca197bffd908 commit r11-9465-gc5bf6dc27cdb091f1f8046f98ce7ca197bffd908 Author: Harald Anlauf <anlauf@gmx.de> Date: Wed Jan 12 21:24:49 2022 +0100 Fortran: fix error recovery on bad structure constructor in DATA statement gcc/fortran/ChangeLog: PR fortran/67804 * primary.c (gfc_match_structure_constructor): Recover from errors that occurred while checking for a valid structure constructor in a DATA statement. gcc/testsuite/ChangeLog: PR fortran/67804 * gfortran.dg/pr93604.f90: Adjust to changed diagnostics. * gfortran.dg/pr67804.f90: New test. (cherry picked from commit 0b8464365b15ac108cd1d00d5bc56d229c1340de)
next prev parent reply other threads:[~2022-01-16 20:40 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-10-01 17:50 [Bug fortran/67804] New: " gerhard.steinmetz.fortran@t-online.de 2015-10-01 17:50 ` [Bug fortran/67804] " gerhard.steinmetz.fortran@t-online.de 2015-10-01 19:00 ` kargl at gcc dot gnu.org 2022-01-12 19:46 ` anlauf at gcc dot gnu.org 2022-01-12 20:30 ` anlauf at gcc dot gnu.org 2022-01-13 18:24 ` cvs-commit at gcc dot gnu.org 2022-01-16 20:40 ` cvs-commit at gcc dot gnu.org [this message] 2022-01-16 20:48 ` anlauf at gcc dot gnu.org 2022-01-25 18:25 ` anlauf at gcc dot gnu.org 2022-01-25 19:37 ` cvs-commit at gcc dot gnu.org 2022-01-25 20:01 ` anlauf at gcc dot gnu.org 2022-03-18 19:54 ` anlauf at gcc dot gnu.org
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-67804-4-7gTaNtVqa9@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).