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/104227] [9/10/11 Regression] ICE virtual memory exhausted: Cannot allocate memory
Date: Wed, 26 Jan 2022 18:02:02 +0000	[thread overview]
Message-ID: <bug-104227-4-pJHcwFSBh4@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104227-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104227

--- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-9 branch has been updated by Harald Anlauf
<anlauf@gcc.gnu.org>:

https://gcc.gnu.org/g:200afb44967520c1c75a35f91c4a56b5e5fb65ff

commit r9-9928-g200afb44967520c1c75a35f91c4a56b5e5fb65ff
Author: Harald Anlauf <anlauf@gmx.de>
Date:   Tue Jan 25 21:56:39 2022 +0100

    Fortran: MOLD argument to TRANSFER intrinsic having storage size zero

    gcc/fortran/ChangeLog:

            PR fortran/104227
            * check.c (gfc_calculate_transfer_sizes): Fix checking of arrays
            passed as MOLD argument to the TRANSFER intrinsic for having
            storage size zero.

    gcc/testsuite/ChangeLog:

            PR fortran/104227
            * gfortran.dg/transfer_check_6.f90: New test.

    (cherry picked from commit ec543c9833c2d9283c035cd8430849eb4ec04406)

  parent reply	other threads:[~2022-01-26 18:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-25 18:02 [Bug fortran/104227] New: [9/10/11/12 " gscfq@t-online.de
2022-01-25 20:46 ` [Bug fortran/104227] " anlauf at gcc dot gnu.org
2022-01-25 20:57 ` cvs-commit at gcc dot gnu.org
2022-01-25 21:04 ` anlauf at gcc dot gnu.org
2022-01-26  8:16 ` marxin at gcc dot gnu.org
2022-01-26 17:13 ` [Bug fortran/104227] [9/10/11 " cvs-commit at gcc dot gnu.org
2022-01-26 17:56 ` cvs-commit at gcc dot gnu.org
2022-01-26 18:02 ` cvs-commit at gcc dot gnu.org [this message]
2022-01-26 18:05 ` 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-104227-4-pJHcwFSBh4@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: link
Be 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).