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/104311] [9/10/11/12 Regression] ICE out of memory since r9-6321-g4716603bf875ce Date: Thu, 03 Feb 2022 18:42:44 +0000 [thread overview] Message-ID: <bug-104311-4-0RfPwhFgL1@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104311-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104311 --- Comment #9 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:4e4252db0348a7274663a892c3a96d3ed7702aff commit r12-7032-g4e4252db0348a7274663a892c3a96d3ed7702aff Author: Harald Anlauf <anlauf@gmx.de> Date: Tue Feb 1 23:33:24 2022 +0100 Fortran: reject simplifying TRANSFER for MOLD with storage size 0 gcc/fortran/ChangeLog: PR fortran/104311 * check.cc (gfc_calculate_transfer_sizes): Checks for case when storage size of SOURCE is greater than zero while the storage size of MOLD is zero and MOLD is an array shall not depend on SIZE. gcc/testsuite/ChangeLog: PR fortran/104311 * gfortran.dg/transfer_simplify_15.f90: New test.
next prev parent reply other threads:[~2022-02-03 18:42 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-31 19:57 [Bug fortran/104311] New: [9/10/11/12 Regression] ICE out of memory gscfq@t-online.de 2022-01-31 19:58 ` [Bug fortran/104311] " gscfq@t-online.de 2022-01-31 20:56 ` anlauf at gcc dot gnu.org 2022-02-01 8:21 ` rguenth at gcc dot gnu.org 2022-02-01 9:08 ` [Bug fortran/104311] [9/10/11/12 Regression] ICE out of memory since r10-653-g6c7ae8c56f9341f1 marxin at gcc dot gnu.org 2022-02-01 13:03 ` [Bug fortran/104311] [9/10/11/12 Regression] ICE out of memory since r9-6321-g4716603bf875ce jakub at gcc dot gnu.org 2022-02-01 13:08 ` marxin at gcc dot gnu.org 2022-02-01 21:33 ` anlauf at gcc dot gnu.org 2022-02-01 22:24 ` anlauf at gcc dot gnu.org 2022-02-01 22:39 ` anlauf at gcc dot gnu.org 2022-02-03 18:42 ` cvs-commit at gcc dot gnu.org [this message] 2022-02-04 19:15 ` cvs-commit at gcc dot gnu.org 2022-02-04 19:18 ` cvs-commit at gcc dot gnu.org 2022-02-04 19:21 ` cvs-commit at gcc dot gnu.org 2022-02-04 19:22 ` 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-104311-4-0RfPwhFgL1@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).