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/100949] [9/10/11/12 Regression] ICE in gfc_conv_expr_present, at fortran/trans-expr.c:1975 Date: Wed, 14 Jul 2021 15:26:00 +0000 [thread overview] Message-ID: <bug-100949-4-BcTWJob4JY@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-100949-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100949 --- 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:269ca408e2839d7f3554a91515d73d4d95352f68 commit r12-2303-g269ca408e2839d7f3554a91515d73d4d95352f68 Author: Harald Anlauf <anlauf@gmx.de> Date: Wed Jul 14 17:25:29 2021 +0200 Fortran - ICE in gfc_conv_expr_present initializing non-dummy class variable gcc/fortran/ChangeLog: PR fortran/100949 * trans-expr.c (gfc_trans_class_init_assign): Call gfc_conv_expr_present only for dummy variables. gcc/testsuite/ChangeLog: PR fortran/100949 * gfortran.dg/pr100949.f90: New test.
next prev parent reply other threads:[~2021-07-14 15:26 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-07 17:33 [Bug fortran/100949] New: " gscfq@t-online.de 2021-06-08 7:46 ` [Bug fortran/100949] " rguenth at gcc dot gnu.org 2021-06-11 12:34 ` marxin at gcc dot gnu.org 2021-07-13 19:25 ` anlauf at gcc dot gnu.org 2021-07-13 19:48 ` anlauf at gcc dot gnu.org 2021-07-14 15:26 ` cvs-commit at gcc dot gnu.org [this message] 2021-07-15 15:57 ` cvs-commit at gcc dot gnu.org 2021-07-16 19:28 ` cvs-commit at gcc dot gnu.org 2021-07-16 19:54 ` cvs-commit at gcc dot gnu.org 2021-07-16 19:55 ` 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-100949-4-BcTWJob4JY@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).