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/104314] ICE in deferred_op_assign, at fortran/resolve.cc:11794 Date: Thu, 15 Sep 2022 20:15:36 +0000 [thread overview] Message-ID: <bug-104314-4-Jh58Grhzi1@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104314-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104314 --- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Harald Anlauf <anlauf@gcc.gnu.org>: https://gcc.gnu.org/g:7bd4deb2a7c1394550610ab27507d1ed2af817c2 commit r13-2690-g7bd4deb2a7c1394550610ab27507d1ed2af817c2 Author: Harald Anlauf <anlauf@gmx.de> Date: Thu Sep 15 22:06:53 2022 +0200 Fortran: error recovery for bad deferred character length assignment [PR104314] gcc/fortran/ChangeLog: PR fortran/104314 * resolve.cc (deferred_op_assign): Do not try to generate temporary for deferred character length assignment if types do not agree. gcc/testsuite/ChangeLog: PR fortran/104314 * gfortran.dg/pr104314.f90: New test. Co-authored-by: Steven G. Kargl <kargl@gcc.gnu.org>
next prev parent reply other threads:[~2022-09-15 20:15 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-31 20:03 [Bug fortran/104314] New: " gscfq@t-online.de 2022-01-31 20:14 ` [Bug fortran/104314] " kargl at gcc dot gnu.org 2022-01-31 21:17 ` sgk at troutmask dot apl.washington.edu 2022-09-05 21:00 ` anlauf at gcc dot gnu.org 2022-09-15 20:15 ` cvs-commit at gcc dot gnu.org [this message] 2022-09-15 20:24 ` 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-104314-4-Jh58Grhzi1@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).